Further, we have to make sure the authorization tokens can be transported to the server. Therefore, add the [[SYSCLS_EXTERNALENTITY|External Entity Classification]] to all meta classes of objects that need external authorization.
[[Category:How-To|Integrate UBIK in an SSO Environment]][[Category:Version 3.6|Integrate UBIK in an SSO Environment]]
= Studio =
An external auth config object specifies for which meta class and sync action (e.g., when uploading instruction documents), which SSO configuration should be used. The result of a correct configuration will be, that the client sends an SSO token to the server when performing the sync action for an instance of the meta class. On the server side, you can use that token to interact with the external system. This only works if there is a scope with the external entity classification for that meta class, because it provides the means to transport the token.
[[Category:How-To|Integrate UBIK in an SSO Environment]][[Category:Version 3.6|Integrate UBIK in an SSO Environment]]
= Client =
</syntaxhighlight>
[[Category:How-To|Integrate UBIK in an SSO Environment]][[Category:Version 3.6|Integrate UBIK in an SSO Environment]]
== SAML ==
[[Category:How-To|Integrate UBIK in an SSO Environment]]
[[Category:Version 3.6|Integrate UBIK in an SSO Environment]]
[[Category:SSO|Integrate UBIK in an SSO Environment]]