Author: James Ressler
Date: June 3, 2024
Audience: Everyone
Environmental details: Self-hosted
Issue
When trying to setup SAML SSO via the root account, the SAML tab is missing.
Solution
Please follow the steps below according to your installation type.
Traditional
Reset the samlconfig on the application server
sudo docker exec -it $(sudo docker ps | grep jamacore | awk '{ print $1 }') rm /home/contour/config/samlconfig sudo replicatedctl app stop —attach sudo docker stop $(sudo docker ps -a -q) sudo systemctl stop docker
Reset the SAML database on the database server
Drop the SAML and OAuth database
While logged into the mysql server with mysql -u root -p
DROP DATABASE saml; DROP DATABASE oauth;
Recreate the SAML and OAuth database
CREATE DATABASE saml; CREATE DATABASE oauth; GRANT ALL PRIVILEGES ON oauth.* TO ‘oauthuser’@‘%’; GRANT ALL PRIVILEGES ON saml.* TO ‘samluser’@‘%’;
Restart services
sudo systemctl start docker systemctl restart replicated replicated-ui replicated-operator
Finally, navigate to the Admin Console and start the application. After it comes back up, login to the root account and reapply the metadata and save the SAML settings.
KOTS
Reset the samlconfig on the application server
kubectl delete svc saml,oauth kubectl delete deploy saml,oauth kubectl delete sts core
Reset the SAML database on the database server
Drop the SAML and OAuth database
While logged into the mysql server with mysql -u root -p
DROP DATABASE saml;
DROP DATABASE oauth;
Recreate the SAML and OAuth database
CREATE DATABASE saml; CREATE DATABASE oauth; GRANT ALL PRIVILEGES ON oauth.* TO ‘oauthuser’@‘%’; GRANT ALL PRIVILEGES ON saml.* TO ‘samluser’@‘%’;
Finally, navigate to the KOTS Admin Console and redeploy the application. After it comes back up, login to the root account and reapply the metadata and save the SAML settings.
Related to
Comments
0 comments
Please sign in to leave a comment.