Re: [Unity-idm-discuss] OAuth authorization request with preselected IdP

[Krzysztof B. <kb...@un...>]

Hi Nick,

W dniu 19.09.2018 o 08:31, Nikolaos Evangelou pisze:
> Hello Krzysztof,
>
> After a long time I tried to enable auto login again and I managed to resolve my issue and I’m posting the solution.
>
> The use case is: Site —>  OAuth authorization request —> Unity AS with autoLogin & authenticator with one IdP —> SAML login —> SAML IdP on Unity
> As I posted earlier I copied the current ${CONF}/modules/oauth/oauth2-as.properties for the new endpoint ${CONF}/modules/oauth/oauth2-sdc.properties.
>
> The oauth2-as.properties has the following properties:
> unity.endpoint.web.authenticationTiles.1.tileContents=pwd cert
> unity.endpoint.web.authenticationTiles.2.tileContents=oauth
> unity.endpoint.web.authenticationTiles.3.tileContents=saml
>
> And oauth2-sdc.properties has:
> unity.endpoint.web.authenticationTiles.1.tileContents=saml
>
> With these properties the flow wasn’t working and when the user returned to Unity was stack in a loop where he/she was asked to login again.
>
> Then I changed oauth2-sdc.properties authenticationTiles number from 1 to 11
> unity.endpoint.web.authenticationTiles.11.tileContents=saml
>
> And then everything worked smoothly.
>
> I guess it was a conflict on authenticationTiles number id because both belong to the same endpoint type (OAuth2Authz/OAuth2Token)



I'm glad it is working. In the meantime there were some changes in that 
feature, related to the major refactoring of how authN screen works. 
Tiles are gone, the current way of configuring and presenting authN 
options is much better. This triggered also an update of the auto-proxy 
feature, which since 2.6.2 release should work in more reliable way 
(triggering and return handling was changed to different, more stable 
approach).


Thanks for the info,
KB