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 TR added without custom RP configuration doesn't work #490
Comments
@yurem |
A bit of update: it's been confirmed that it also doesn't work for TR of type "Federation", and in this case even adding Custom RP config to it doesn't fix the issue. |
@aliaksander-samuseu Thanks for the note. |
Federal case: UI calls save(); create second thread for metadata downloading and process metadata for isFederal() checking in first thread. But metadata in second thread isn't downloaded yet... |
…adata parsing race condition localization
@dmogn is this issue fixed? |
@willow9886 |
[20:53:18] Alex Samuseu: Here is a problem in the latest 3.1 build. When I create SAML TR of type federation, it passes metadata validation, but nevertheless is shown as TR of type "site" in the list, and I can't use it to create other TRs based on it as before. |
…adata parsing race condition localization
…ove asynch URL metadata downloading (thread race condition)
Reopening it as it's been designated for 3.0.2 and I still can reproduce it in my release deb pakage. Fed metadata's element is not added to |
Closing this as won't fix. In 3.0 it is required to click on Configure Relying Party |
Environment:
CentOS 6.7, Gluu CE 3.0.1-1-3
Preconditions:
Gluu was installed with full set of modules
Steps to reproduce:
uid
,transientid
andemail
attributes.# service idp restart
Result:
After user is redirected to IdP it responds with "Application is not registered" error page. In
idp-process.log
messages like this appears (note the "No metadata returned" part):grepping for SP's hostname shows, that in case when TR is created without custom RP settings entry for this SP is not added to
/opt/shibboleth-idp/conf/metadata-providers.xml
Without it:
With it:
You can view full screen capture here
Expected result:
If custom RP properties are not specified TR is still functional, has corresponding entry in
/opt/shibboleth-idp/conf/metadata-providers.xml:
file and default RP configuration provided in/opt/shibboleth-idp/conf/relying-party.xml
is used for it.The text was updated successfully, but these errors were encountered: