...
| Page Properties | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
Resources & Remarks
This article needs more information and especially a corresponding tutorial, building an example client. Andreas Schulz made a tutorial video, Which should be put in a separate tutorial page, together with a good description outlining the topics it covers and linked to this concept article. The link to the documentation is also not final and subject to change. Modification History
|
...
A short introduction is given here:
| Widget Connector | ||
|---|---|---|
|
Running Clients outside the yuuvis® Momentum cluster
By default, client applications built with @yuuvis/core library are supposed to be deployed inside the yuuvis® Momentum cluster. As a main advantage, there is no responsibility for the library to handle the authentication process. Users authenticate directly via the AUTHENTICATION service.
As of yuuvis® Momentum version 2021 Autumn, the @yuuvis/core library allows for the built of clients that can be deployed outside the yuuvis® Momentum cluster. Such clients authenticate via OpenID Connect to the AUTHENTICATION service and can thus be hosted fully independently. They can even be configured to support switching between different yuuvis® Momentum clusters. Users select the cluster to which they want to connect.
An example project is provided on GitHub.
The following configuration steps are required to allow for the client deployment outside a yuuvis® Momentum cluster.
Setup Keycloak
Configure a Client inside your Keycloak Realm that will be used to trigger login.
| Code Block | ||
|---|---|---|
| ||
Client ID: 'spa-client' // choose your own name
Client Protocol: 'openid-connect'
Access Type: 'public'
Valid Redirect URIs: // match your environment
Web Origins: '+' // means: everything that's also invalid redirect uris
Advanced Settings
Proof Key for Code Exchange Code Challenge Method: 'S256'
|
Setup Project
Choose one of the following ways to setup your project.
Setup via 'oidc.json' Configuration File
Create a file oidc.json with the following content in the root directory of your assets folder.
| Code Block | ||
|---|---|---|
| ||
// ./src/assets/oidc.json
{
"host": "https://kolibri.enaioci.net", // yuuvis backend URI
"tenant": "kolibri", // yuuvis tenant (equals Keycloak realm)
"issuer": "https://auth.enaioci.net/auth/realms/kolibri",
"clientId": "spa-client",
}
|
Setup via Module Configuration
During the import of YuvCoreModule, specify the following configuration.
...
| language | yml |
|---|
...
:
...
Setup via Dynamic Initialization
In case you do not know about the OIDC properties when your application starts (the OIDC profile needs to be loaded or users select one of several profiles), you will just import YuvCoreModule without OIDC config. The @yuuvis/core library will try the default initialization as if the client were deployed within a yuuvis® Momentum cluster. This will cause some console errors which can be ignored.
Once you are ready to specify the OIDC configuration, you can re-trigger the initialization of the library's core module:
...
| language | yml |
|---|
...
Summary
You have been pointed to the yuuvis® Momentum client libraries, which facilitate the rapid development of your own custom client application in Angular.
...