The Altair Community is migrating to a new platform to provide a better experience for you. In preparation for the migration, the Altair Community is on read-only mode from October 28 - November 6, 2024. Technical support via cases will continue to work as is. For any urgent requests from Students/Faculty members, please submit the form linked here

"RMSSOAuthenticator error, failed to load IDP configuration" error

sumancologysumancology Member Posts: 5 Contributor I
in Help
I am trying to install RM AI Hub 9.8 on a linux server using the docker-compose system.  I cannot get pass the "RMSSOAuthenticator error, failed to load IDP configuration" error. The generic documentation provided in the docker are not very helpful. Can anyone point me to a sample (.env) and (docker-compose.yml) files that I could modify. I am using PostgreSQL

Answers

  • MartinLiebigMartinLiebig Administrator, Moderator, Employee-RapidMiner, RapidMiner Certified Analyst, RapidMiner Certified Expert, University Professor Posts: 3,533 RM Data Scientist
    Hi,
    if you are a customer or partner please message your customer success or partner manager. We are of course happy to support you directly.

    Best,
    Martin
    - Sr. Director Data Solutions, Altair RapidMiner -
    Dortmund, Germany
  • sumancologysumancology Member Posts: 5 Contributor I
    edited March 2021
    Can anyone offer any suggestions to resolving the "RMSSOAuthenticator error, failed to load IDP configuration" error?  I have tried RM customer service several times for help, each time they direct me back to the community forum.  I am wondering if this is a software issue.  Has anybody faced this issue when installing RM AI Hub on linux server?
  • BalazsBaranyBalazsBarany Administrator, Moderator, Employee-RapidMiner, RapidMiner Certified Analyst, RapidMiner Certified Expert Posts: 955 Unicorn
    Hi @sumancology,

    this is an error coming from the authentication component (Keycloak) and RM Server not working together correctly. I see this from time to time when restarting the deployment (e. g. after a Docker software update or a server restart). 

    I don't know a fool-proof way to fix it but here are some hints:
    "docker-compose logs -f rm-keycloak-svc" will tell you if Keycloak is running properly. In my case it was sometimes hanging in a restart loop.
    You might be able to successfully stop rm-keycloak-db-svc and rm-keycloak-svc and start them later. Also try with the other components, e. g. rm-proxy-svc, rm-server-svc.

    After starting the entire deployment it is normal to wait a few minutes until everything is in place.

    Regards,
    Balázs

Sign In or Register to comment.