Skip to content
This repository has been archived by the owner on Mar 3, 2022. It is now read-only.

Supporting the hybrid flow #427

Closed
mukhtar opened this issue Oct 1, 2017 · 8 comments
Closed

Supporting the hybrid flow #427

mukhtar opened this issue Oct 1, 2017 · 8 comments
Labels

Comments

@mukhtar
Copy link

mukhtar commented Oct 1, 2017

I’m making use of this library and wanted to ask a little about support for the hybrid flow. I’ve read the issues that exist on this topic and I understand that the plan is not to support for this flow.

I have a couple of questions that I hope you can help me with.

  1. Can you suggest any other libraries that are similar oidc-client-js that support the hybrid flow? I’e come across AppAuth-JS but this seems to target chrome apps and electron which my application is not (simple browser based web app).

  2. How much work would be involved, in your opinion, to extend oidc-client-js to support hybrid flow? If I wanted to do this myself, are you able to point me in the right direction please?

@brockallen
Copy link
Member

Hybrid flow is not designed for browser-based apps. Why do you want to use it for that scenario?

@mukhtar
Copy link
Author

mukhtar commented Oct 1, 2017

I think I was unclear when I said 'browser based'.

I'm working on two apps. One is a traditional web application where web pages are rendered server side and there is some element of client side logic. The other is more of SPA.

For the former, from what I can tell, it would be necessary for the server to be able to get the id and access tokens using the authorisation code, thus the hybrid flow would be useful. For the latter, the implicit flow would suffice.

From your experience, do you see this library (oidc-client) being used for traditional web apps where web pages are rendered server side? Is a client side openid connect library even necessary?

@brockallen
Copy link
Member

From your experience, do you see this library (oidc-client) being used for traditional web apps where web pages are rendered server side

No, because it's specifically designed for client-side browser-based JS apps. If you want something server-side, then there are already tons of other OIDC frameworks for that.

@mukhtar
Copy link
Author

mukhtar commented Oct 11, 2017

Thanks. How much work would be involved, in your opinion, to extend oidc-client-js to support hybrid flow? If I wanted to do this myself, are you able to point me in the right direction please?

@brockallen
Copy link
Member

No, sorry, I don't have the bandwidth. If you're looking to hire us for consulting services, or sponsor features then let us know.

@benpolinsky
Copy link

@NathanStrutz
Copy link

@mukhtar

Thanks. How much work would be involved, in your opinion, to extend oidc-client-js to support hybrid flow? If I wanted to do this myself, are you able to point me in the right direction please?

I bet you can do most of that by just cloning and reverting 10b58d7. 😃

@brockallen
Copy link
Member

No. There's more validation to be performed, and supporting id_token on the front channel and then on the back channel adds complexity that I don't have time to consider.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

No branches or pull requests

4 participants