You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be really nice to have an API endpoint, where Jagger can receive a public metadata url of an IdP (of course after API authentication) and if the metadata downloaded by Jagger from the posted url is valid, it can be added to the Jagger automatically, e.g. in a pendig status, or to the test-federation.
This feature would be relevant for the NRENs which provide "IdP as a Service" opportunity to their institutions. These institutions have probably lack of knowledge about either operating an own IdP so doing the technical part of integrating an IdP to a federation. In this case the IdPaaS would be able to preregister an IdP on behalf of such a "SAML-poor" :) institution.
The text was updated successfully, but these errors were encountered:
@sitya thanks for starting this issue. This would be an immensely useful feature for "SAML-naive" :-) users of our eduid.africa hosted IdP service. We currently have to do this manually and had it on our list of todos.
It would be really nice to have an API endpoint, where Jagger can receive a public metadata url of an IdP (of course after API authentication) and if the metadata downloaded by Jagger from the posted url is valid, it can be added to the Jagger automatically, e.g. in a pendig status, or to the test-federation.
This feature would be relevant for the NRENs which provide "IdP as a Service" opportunity to their institutions. These institutions have probably lack of knowledge about either operating an own IdP so doing the technical part of integrating an IdP to a federation. In this case the IdPaaS would be able to preregister an IdP on behalf of such a "SAML-poor" :) institution.
The text was updated successfully, but these errors were encountered: