Advice on cross-domain localization

[aspnet-hello]

From @Ponant on Sunday, June 11, 2017 11:42:45 PM

Hello,
I have two websites and one is used as an IdentityServer, where user login to enter credentials or register and where he is redirected back to the second website after. Each website lives on a different domain but I can also target them to sub-domains of a main domain if that is a needed.

Localization is implemented successfully on each website with a dropdown button for the cultures. What I would like is, when a user comes to the website 2, chooses a culture (say DE) and decides to login, I want him to be redirected to IdentityServer with culture DE instead of the default.
I welcome any hint on how to achieve this?

Copied from original issue: aspnet/Localization#382

[aspnet-hello]

From @hishamco on Monday, June 12, 2017 4:42:57 AM

Frankly I didn't work with Identity server, but if there's a way to pass the culture to the identity server, you could simply append the culture to the querystring when you redirect to other website

I'm happy to hear from @damienbod which wrote a lot of great blog posts about the Identity Server and localization

[aspnet-hello]

From @Ponant on Monday, June 12, 2017 5:02:39 AM

@hishamco , thank you for your answer and hint. Any link to blog posts on identityserver+localzation would be great as a start; a quick google search returns nothing at first attempt.

[aspnet-hello]

From @Eilon on Monday, June 12, 2017 10:09:54 AM

Using a query string parameter is probably the best approach here. I think that the security middleware has callback events where you can add additional data to the authentication process, which would get transferred to the authentication server.

@Tratcher - do you know the secret sauce to pass additional data to the auth server? It seems that there are OAuth-standard request parameters for things like "ui locale".

[aspnet-hello]

From @Tratcher on Monday, June 12, 2017 11:34:34 AM

OAuth2 or OpenIdConnect? The process is similar.

For OAuth2 you implement the OnRedirectToAuthorizationEndpoint event and tack your parameters onto the already assembled RedirectUri.
https://github.com/aspnet/Security/blob/rel/1.1.2/src/Microsoft.AspNetCore.Authentication.OAuth/Events/OAuthEvents.cs#L23

For OpenIdConnect it's OnRedirectToIdentityProvider where you add your custom parameters to the ProtocolMessage.
https://github.com/aspnet/Security/blob/rel/1.1.2/src/Microsoft.AspNetCore.Authentication.OpenIdConnect/Events/OpenIdConnectEvents.cs#L33

[aspnet-hello]

From @Ponant on Monday, June 12, 2017 11:46:56 AM

Thanks @Eilon and @Tratcher , I thought that modifying the endpoint is not a secure procedure. I recall having read something like this on the IdenttityServer repo but cannot find the thread anymore. Perhaps @leastprivilege could comment on the reliability of the procedures mentioned above.

[aspnet-hello]

From @Ponant on Tuesday, June 20, 2017 1:47:41 AM

Hi @Tratcher, can you point to some example using the Funcs you refer to? Cheers

[aspnet-hello]

From @hishamco on Tuesday, June 20, 2017 4:00:58 AM

Have a look to the test project here and there

[aspnet-hello]

From @Ponant on Tuesday, June 20, 2017 2:05:10 PM

Thanks @hishamco I will look at that, then.

[hishamco]

@mkArtakMSFT I think we need to close this issue while it's answered

[aspnet-hello]

We periodically close 'discussion' issues that have not been updated in a long period of time.

We apologize if this causes any inconvenience. We ask that if you are still encountering an issue, please log a new issue with updated information and we will investigate.