...
Make sure, that you do not already have section for camp and Keykloak in your values file. If so, replace them.
Configure the connection to the OIDC provider for Smartfacts
In the “global” global section of your values file add the information of you OIDC provider:
...
| Info |
|---|
With Azure AD as OIDC provider it is necessary to add the path “https://graph.microsoft.com/oidc/userinfo“ to the property spa.cspConf.externalUrls. This will add the URL to the list of allowed CORS origins. |
Configure the connection to the OIDC provider for the OSLC Connector for Smartfacts
To connect the OSLC Connector for Smartfacts with your OIDC provider, add the following properties in the genoslc.env section of your values file for the Smartfacts deployment, as seen below:
| Code Block |
|---|
authorizationUri: "<Authorization URL of identity provider>"
tokenUri: "<Token URI of identity provider>"
userInfoUri: "<UserInfo URI of identity provider>" |
Replace the placeholder in authorizationUri, tokenUri and userInfoUri with the appropriate URLs of your identity provider instance
Adopting to custom token claims
...
| Code Block |
|---|
global:
lcam:
rules:
- claimgroupName: "emailSmartfacts Users"
valueclaim: "email"
value:
- "@" groupName: Smartfacts Users- "@"
groupLicence:
- "LIC_SMARTFACTS_USER"
accountName: "Smartfacts Account"
- claimgroupName: "emailAccount Administrators"
valueclaim: "email"
- accound.administrator@your.domainvalue:
groupName: Account Administrators- "account.administrator@your.domain"
groupLicence:
- "LIC_SMARTFACTS_USER"
accountName: "Smartfacts Account" |
To adopt the rules to your environment, configure the necessary information in the file.
...
| Code Block |
|---|
sudo helm upgrade --install --timeout 20m0s smartfacts mid-smartfacts/smartfacts -f values.yaml -f group-rules.yaml --version 4.67.05-genoslcv2 -n smartfacts --create-namespace |
...