HI Jiyong He - can you please give us more details as to what you are trying to achieve exactly? Explain "set okta as the default authentication provider" - what is the behaviour you expect?

Lastly, please provide more details on how the GroupShare Online Editor is integrated with your own web site? GroupShare Online Editor is part of GroupShare - and they both run on IIS. So I am not exactly sure how can you integrate the Online Editor with "own web site".

When you installed GroupShare yourselves, did you create an installation protocol documenting all the steps and configuration that you had to do? That would help us understand this better.

Thank you

Adrian

Thanks!

our Groupshare was deployed by SDL vendor.

we have a business site,our translator login from this site, and then, traslator click one button at this website, the file be translated to groupshare through restful api，then open the file in the online editor, and the translator starts to translate，so we need to integrate website and groupshare to do SSO, Is there a similar solution or how can we do that?

Hi Jiyong He - who is the vendor that installed GroupShare for you? Every GroupShare installation needs to have an installation protocol or document as I mentioned. Do you have that document? If not, can you ask the vendor if they created one to send it to you?

From what you are saying GroupShare was already integrated with Okta, which means that also Online Editor is integrated with Okta. Which means on your GroupShare server in the file loginProvidersConfig.json from : C:\Program Files (x86)\SDL\SDL Server\Web\resources you have probably 2 providers. If you only leave only the Okta one, then when you access the GroupShare website or an Online Editor link, it will automatically redirect to Okta. However, keep in mind that will mean that no SDL login will be possible anymore.

Hi  Adrian Boloveschi, Trados SDL in china local region deploy  groupshare for us, we have that Document

there's  really 2 providers in the file loginProvidersConfig.json, but when we only leave the Okta provider, and restart groupshare and IIS, the button in the login page is disabled,Or when there's only okta provider, the login page of groupshare is no longer available, only login from okta？

Hi  Adrian Boloveschi, Trados SDL in china local region deploy  groupshare for us, we have that Document

there's  really 2 providers in the file loginProvidersConfig.json, but when we only leave the Okta provider, and restart groupshare and IIS, the button in the login page is disabled,Or when there's only okta provider, the login page of groupshare is no longer available, only login from okta？

Hi Jiyong He, you should not remove the GS authentication provider from the config file but have Okta as a second option. Please take note that GroupShare only works for IDP initiated login so all GS would do if you select OKTA in the login screen is to redirect you to the authentication provider.

You can skip this entirely if you make users go to your Okta page first and then select GroupShare - the users would then directly get into the application without further promts (assuming they already have a role associated in GroupShare). If you would like to receive assistance by SDL Professional Services, we could arrange a session with you to look at the configuration and consult on what you can do and what you cannot do with GroupShare and custom authentication providers. This type of in-session consultation however would need to get charged by the hour. Please let us know if we can assist you and we will get in touch with a quote on SSO consultation. If configuring SSO was agreed to be part of your PS installation however we can check if there was something missing - if so, this would probably be covered by your installation package. Can you maybe raise a support request where you supply information on who installed and what was done - I then could reach out to colleagues to clarify...