[keycloak-dev] portal identity experiences

[Bill Burke]

On 9/16/2013 11:51 AM, Boleslaw Dawidowicz wrote:
>
> On Sep 16, 2013, at 3:09 PM, Bill Burke <bburke at redhat.com> wrote:
>
>>> We have some. Which aspect are you interested in? Majority of
>>> deployments are around integrating MSAD - as majority of organizations
>>> just inherit it as part of Windows Domain.
>>>
>>
>> They used portal as an identity broker to MSAD?  What did they use MSAD
>> for?  User metadata and credentials?  Or was application security
>> metadata in their too?  (roles/role mappings).
>
> No identity broker. Mainly there were two use cases
> - LDAP integration. MSAD is still most popular one. Major requirement is around authentication and being able to tied roles membership store there with security. All sorts of LDAP schema shapes involved.

So, Portal *WAS* a broker using MSAD as storage.

> - SSO integration with already deployed frameworks. Most popular are Web SSO solutions. Then there is SAML for more specific cases. Using JAAS always helped as it allowed easily plugging in custom solutions
>

Portal as the central auth SSO server?

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com