WHAT

Set ssoprovider & ssobaseurl flag in app-interface

UPDATE:

• We already have a flag for the ssobaseurl, it's set with a flag called 'redhat-sso-base-url'. It is also already set in the saas-template (MAS_SSO_BASE_URL).

WHY

mas-sso to sso migraiton

HOW

• Add a flag to the KeycloakConfig for setting the sso provider.
  • There is already a field called SelectSSOProvider in the KeycloakConfig which can either be set to mas_sso or redhat_sso. The flag should set the value of this field as it is used for reading the correct credentials depending on the SSO provider type used.
  • The default value should be 'mas_sso', same as it is right now.
  • There should also be validation added for this to ensure it can only either be set to 'mas_sso' or 'redhat_sso'.
• Add a new env var in our service template for the sso provider
• Add the env vars for ClientIDFile and ClientSecretFile to the service template as well.
• Add the sso provider env var and the other env vars to stage + prod of the saas template.
• Validate that the value can only be 'mas_sso' and 'redhat_sso'.
• Add to Makefile and update documentation

DONE

• ssoprovider flag default should be set to 'mas_sso'
• sso provider env var added to stage + prod of the saas template, it should be set to 'mas_sso'
• Current unit/integration tests around this feature reviewed and modified if necessary or added if none exists.

Guidelines

The following steps should be adhered to:

• Required tests should be put in place - unit, integration, manual test cases (if necessary)
• CI and all relevant tests passing
• Changes have been verified by one additional reviewer against:
• each required environment
• each supported upgrade path
• If the changes could have an impact on the clients (either UI or CLI), a JIRA should be created for making the required changes on the client side and acknowledged by one of the client side team members. PR has been merged