-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SAML Metadata URL did not connect and pull data successfully #27072
Comments
@jianlinz What Mattermost server version are you on? |
Thanks |
Thank you, given that v8.1 has gone out of support on May 15th, would you be open to upgrading to v9.5 or a newer version to see if the issue still reproduces? |
ok ,I'll switch to version 9.8 and try it out |
mattermost 9.8 I also tried to integrate keycloak with OpenId. I also tried to integrate openId with gitlab integrate openId with keycloak4.5 Can you tell me what I did wrong? |
Would you be open to posting about this on one of our troubleshooting forums, either at https://community.mattermost.com/core/channels/peer-to-peer-help or at https://forum.mattermost.com/? |
Summary
The SAML integrated Keycloak Identity Provider Metadata URL authentication fails
Steps to reproduce
Configure keycloak and mattermost based on the following addresses
get keycloak /realm-settings->SAML 2.0 Identity Provider Metadata URL
mattermost/admin_console/authentication/saml ->Identity Provider Metadata URL-> SAML 2.0 Identity Provider Metadata URL
click button 'Get SAML Metadata From IdP'
show error message - > SAML Metadata URL did not connect and pull data successfully
mattermost log
Expected behavior
successfully
Observed behavior (that appears unintentional)
SAML Metadata URL did not connect and pull data successfully
Possible fixes
Since these Settings are the most basic Settings, can you tell me if I did something wrong and I understand that success should be displayed at least in this step.
The SAML 2.0 Identity Provider Metadata URL is accessible from a browser.
The text was updated successfully, but these errors were encountered: