You could make your own Integrator and do set the language in the SynchronizeUser method
Yeah, that's a solution. I thought though that there would be a setting for that.
// Regards, Torbjörn
I'm thinking of writing my own Integrator. But I can't find where the Integrator/SynchronizeUser is called/configured.
I'd be very thankful if someone could point me in the right direction.
Thanks, Josef
<system.webServer> <modules runAllManagedModulesForAllRequests="true"> <add name="InitializationModule" type="EPiServer.Framework.Initialization.InitializationModule, EPiServer.Framework" preCondition="managedHandler"/> <add name="FirstBeginRequestModule" type="EPiServer.Web.InitializationModule, EPiServer" preCondition="managedHandler"/> <add name="Initializer" type="EPiServer.Scheduler.Initializer, EPiServer.Scheduler" preCondition="managedHandler"/> <add name="WorkflowRuntime" type="EPiServer.WorkflowFoundation.WorkflowSystem, EPiServer.WorkflowFoundation" preCondition="managedHandler"/> <add name="UrlRewriteModule" type="EPiServer.Web.UrlRewriteModule, EPiServer" preCondition="managedHandler"/> <add name="ShellRoutingModule" type="EPiServer.Shell.Web.Routing.ShellRoutingModule, EPiServer.Shell"/> <add name="EPiServerCommon" type="EPiServer.Common.Web.HttpModule, EPiServer.Common.Web" preCondition="managedHandler"/> <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" preCondition="managedHandler"/>
<add name="EPiServerCommunity" type="EPiServer.Community.Web.Administration.CommunityModule, EPiServer.Community.Web.Administration" preCondition="managedHandler"/>
<add name="EPiServerMail" type="EPiServer.Mail.Core.Web.MailModule, EPiServer.Mail.Core.Web" preCondition="managedHandler"/>
<!-- <add name="EPiServerCommonWindowsAuthenticationIntegration" type="EPiServer.Common.Web.Authorization.IntegrationHttpModule, EPiServer.Common.Web.Authorization" preCondition="managedHandler" />-->
<add name="EPiServerCommonWindowsAuthenticationIntegration" type="Itera.WinAdSecurity.OwnIntegrationHttpModule, Itera.WinAdSecurity" preCondition="managedHandler"/>
Great, thanks for quick reply. I'll try to get it working. Is it posible to just extend existing module with own code, or do I have to create my own module from scratch by reflecting existing binaries?
Think you need to do some reflection, but most can be used as is.
Dont remeber all the details, sorry
Perhaps it's possible to just hook the SecurityHandler CreatedUser / UpdatedUser events and set the culture there, so you don't have to mess around with the integrator.
Magnus, thank you for your input. I actually hijacked this thread to find out more about how to override the Integrator. My problem is different than the original post about culture. I posted my problem in a new thread. Perhaps you can read it and give me your thoughts? I don't know if the Integrator is the correct path to follow...?
Hi,
We're using the MultiplexingRoleProvider (provider1="EPiServerCommonRoleProvider" provider2="WindowsRoleProvider") and MultiplexingIntegrationMembershipProvider (provider1="EPiServerCommonMembershipProvider" provider2="WindowsMembershipProvider"), and has set roleToSynchronize1 to "1*". The site has multiple sites (one for each country, since the content is quite different).
When a user is added to the Common database when logging in through the WindowsRoleProvider/WindowsMembershipProvider, the user gets the en-US culture, independent of the culture that is set for the site that the user logs on to.
How do I configure our setup so that the user gets the same culture in the Common database as the site the user has logged on?
// Kind regards, Torbjörn