Skip to content
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

Usage scenario of PAIA/auth and Shibboleth #52

Closed
lahmann opened this issue Apr 30, 2015 · 5 comments
Closed

Usage scenario of PAIA/auth and Shibboleth #52

lahmann opened this issue Apr 30, 2015 · 5 comments

Comments

@lahmann
Copy link

lahmann commented Apr 30, 2015

Is there any solution at hand to use a PAIA webservice in combination with Shibboleth if the PAIA webservice is queried by a client which got authorized through Shibboleth? Or is this a scenario where #42 (comment) would apply?

@nichtich
Copy link
Member

nichtich commented May 4, 2015

I am not familiar with Shibboleth so a more detailed user story would help to judge. However I suppose that Shibboleth can be supported as alternative authentification method by replacing PAIA auth with another service. I am not sure about the relationship between OAuth2 and Shibboleth, maybe general support of OAuth2 (#51) could further simplify support of Shibboleth.

@tzeumer
Copy link

tzeumer commented Jun 17, 2016

I wonder, exists a solution now? Maybe with a how to? :)

@olli-gold
Copy link

olli-gold commented Jun 17, 2016

With an admittedly limited knowledge of Shibboleth I guess that supporting Shibboleth for PAIA would require a Service Provider implementation, which could generate the access token for PAIA and an Identity Provider containing the patron authentication information. For any PAIA request the access token could get used. But I guess there is no Service Provider implemented yet, bypassing PAIA Auth to generate an access token. Or am I wrong with that?

@nichtich
Copy link
Member

olli-gold is right. To further integrate Shibboleth and PAIA and documentation, a use case with an existing Identity Provider is needed. But I think that OAuth comes first.

@nichtich
Copy link
Member

nichtich commented Mar 8, 2017

This ins unlikely to make it into the specification. See #62 for plans for further integration of OAuth instead.

@nichtich nichtich closed this as completed Mar 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants