On Mon, Nov 11, 2013 at 1:01 PM, Prabath Siriwardena <[email protected]>wrote:

>
>
>
> On Mon, Nov 11, 2013 at 11:47 AM, Johann Nallathamby <[email protected]>wrote:
>
>>
>>
>> Yes, we don't have to encrypt the consumer key, but still I feel we can
>> use a different identifier to uniquely identify the application rather than
>> consumer key. There is no reason to consider OAuth special consideration
>> here. [?]
>>
>
> Do not relate this to Oauth. We need to have unique identifier to the
> application. So that is a client id - and it will become the client id as
> when oauth enabled. Almost all the application will have oauth enabled by
> default.
>

Then it should be the same for SAML SSO as well right? All applications
should be SAML SSO enabled by default..?


>
> Thanks & regards,
> -Prabath
>
>
>> Or else if we could have user defined names that are meaningful as the
>> consumer key, like "Johann'sPlaygroundApp", and use the same as entity Id
>> when registering a SAML SSO service provider, and wherever we uniquely
>> identify the application that also seems fine with me. In fact our APIs
>> allow us to specify consumer keys and I have seen other products that
>> allows us to do this. Only consumer secrets are auto generated.
>>
>>>
>>> Thanks & regards,
>>> -Prabath
>>>
>>>
>>>>
>>>>
>>>>>
>>>>> 5. Would this change the Identity Server Management Console UI ?
>>>>>
>>>>> Yes. We need to have a tab for defining and listing Applications. Also
>>>>> other tabs also need to absorb the Application concept while grouping.
>>>>>
>>>>> 6. How does this differ from the Application we create in API Manager ?
>>>>>
>>>>> It's the same + more capabilities.
>>>>>
>>>>> 7. How does this relate to Web Applications we host in Application
>>>>> Server ?
>>>>>
>>>>> Its the same. You define QoS parameters for those applications from
>>>>> this.
>>>>>
>>>>
>>>>> Ideas, thoughts, questions mostly welcome..
>>>>>
>>>>> Thanks & regards,
>>>>> -Prabath
>>>>>
>>>>> _______________________________________________
>>>>> Architecture mailing list
>>>>> [email protected]
>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Thanks & Regards,
>>>>
>>>> *Johann Dilantha Nallathamby*
>>>> Senior Software Engineer
>>>> Integration Technologies Team
>>>>  WSO2, Inc.
>>>> lean.enterprise.middleware
>>>>
>>>> Mobile - *+94777776950*
>>>> Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>*
>>>>
>>>> _______________________________________________
>>>> Architecture mailing list
>>>> [email protected]
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>>>
>>> --
>>> Thanks & Regards,
>>>
>>> Prabath
>>>
>>> Mobile : +94 71 809 6732
>>>
>>> http://blog.facilelogin.com
>>> http://RampartFAQ.com
>>>
>>> _______________________________________________
>>> Architecture mailing list
>>> [email protected]
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> *Johann Dilantha Nallathamby*
>> Senior Software Engineer
>> Integration Technologies Team
>>  WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - *+94777776950*
>> Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>*
>>
>> _______________________________________________
>> Architecture mailing list
>> [email protected]
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Thanks & Regards,
> Prabath
>
> Mobile : +94 71 809 6732
>
> http://blog.facilelogin.com
> http://RampartFAQ.com
>
> _______________________________________________
> Architecture mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Senior Software Engineer
Integration Technologies Team
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+94777776950*
Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>*

<<335.png>>

_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to