Changes
With this, the {{UBIK}} session in the web service's {{UBIK}} Environment is tagged with the SSO token, and the customizing code can use it to interact with 3rd party systems.
= Studio =
=== Applying an SSO Processor ===
<div class="mw-collapsible mw-collapsed" style="width:100%; overflow:auto;"><div style== "font-weight:bold;line-height:1.6;">OIDC </div><div class===="mw-collapsible-content">
{{Version/ServerSince|4.6.0}}In the case of a periodic rolling of the signing key, use the DynamicOIDCProcessor which fetches the JWKS automatically via the base URL of the chosen OIDC Provider:
<syntaxhighlight lang="csharp">
You will need to insert the correct jwks from your OIDC Provider instead of "...".
</div></div> <div class="mw-collapsible mw-collapsed" style="width:100%; overflow:auto;"><div style== "font-weight:bold;line-height:1.6;">SAML </div><div class===="mw-collapsible-content"><syntaxhighlight lang="csharp">
public override UBIK.Kernel.SSO.ISSOProcessor GetSSOProcessor(System.String token)
{
There are several use-cases where we need to customize the SSO processor. We can define what should be done when a login object is required or found, and we can use the information delivered with the SSO token in the form of assertions or claims. In any case, we must override the SSO processor implementation, e.g.:
<syntaxhighlight lang="csharp" class="mw-collapsible mw-collapsed">
public class MyOIDCProcessor : DynamicOIDCProcessorExt
{
}
</syntaxhighlight>
</div></div>
== Interfacing ==
}
</syntaxhighlight>
= Client =
