Developer forum

Forum » CMS - Standard features » SSO with multiple instances

SSO with multiple instances

E-mail notifications
Nuno Aguiar Dynamicweb Employee
Nuno Aguiar
Reply
Posted on 09/04/2024 10:55:42

Hi,

 

The UI allows us to create multiple instances of SSO for the same provider, but looking at the OwinStartup class it looks that it only registers the first it can find, even if disabled (It should be using GetActiveProviders()).

Is this by design or a bug?

 

Why is this important?

I spent some time trying to debug a customer's SSO credentials, and without having an account with their Azure AD, I had to use our own settings. Between discovering I had to do an IIS reset and this, I spend some time spinning my wheels.

It would be great to:

  • Add some infor/warning that an IIS is needed for changes to take effect
    (since it's not common, it's easy to forget)
  • Allow for multiple providers of the same type OR prevent multiple providers from the same type from being created

 

Best Regards,

Nuno Aguiar


Replies

 
Nicolai Pedersen Dynamicweb Employee
Nicolai Pedersen
Posted on 09/04/2024 16:20:39
Reply

Hi Nuno

We will take this into consideration when we re-implement this on DW10

BR Nicolai

 
Nuno Aguiar Dynamicweb Employee
Nuno Aguiar
Posted on 09/04/2024 17:04:07
Reply

Sounds perfect Nicolai. Thanks

 
Justin Sjouw Dynamicweb Employee
Justin Sjouw
Posted on 01/04/2025 11:42:18
Reply

Hey NP,

I think SSO is not yet implemented in DW10, is it on the roadmap for backend and or frontend?

Thanks,

Justin

 
Nicolai Pedersen Dynamicweb Employee
Nicolai Pedersen
Posted on 01/04/2025 14:55:28
Reply

SSO is coming end April with these providers - this is already in testing:

  • Microsoft Entra (login.microsoft.com)
  • Azureb2c (b2clogin.com)
  • Github

Further we have Google and OKTA in the roadmap, ETA maybe for end April, otherwise end May.

BR Nicolai

 
Nuno Aguiar Dynamicweb Employee
Nuno Aguiar
Posted on 01/04/2025 15:05:16
Reply

Hi Nicolai,

 

I know that for DW9 SSO was limited to 1 single setup per Provider; meaning if we needed to have multiple Azureb2c configurations, it would only use the first one (even if it was disabled). We had this issue on projects with multiple websites.

 

Do you know if this has been addressed?

 

BR

Nuno Aguiar

 

You must be logged in to post in the forum