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

use-html-parser-for-login-flow is awesome, and chance you will pull that into master #38

Open
markdanko opened this issue Aug 19, 2019 · 5 comments

Comments

@markdanko
Copy link

any plan to move use-html-parser-for-login-flow back into master.

If not, If I add a config option for use-html-parser-for-login-flow, or the default, are you likely to accept such a change to master?

@mgreyo
Copy link
Contributor

mgreyo commented Aug 19, 2019

Hey Mark,

We haven't removed any functionality, we have just added the support for authenticating via Azure AD (which in some cases has MFA, and cannot be parsed automatically for you). Apart from that, the only other change was how to start the auth server; the part that implements the "use-html-parser-for-login-flow" I think you're referencing. It is now osprey serve auth <options>.

To use it as it was previous to v2.0 you should configure the osprey: section of the config, and skip the Azure AD section, and issue the commands as usual: osprey user login.

Feel free to correct me if I'm wrong, and if you feel the README was lacking in detail please let us know!

@markdanko
Copy link
Author

markdanko commented Aug 19, 2019

sorry if I am confused. my understanding is with master you need to change the dex web/static and web/themes/ (which causes other problems for me #20 ), but with the branch use-html-parser-for-login-flow, you do not need to.
Right now, I am building/using that branch. Are you saying there is way to choose that option in master?

@mgreyo
Copy link
Contributor

mgreyo commented Aug 20, 2019

Sorry for the misunderstanding. I wasn't aware of that branch 🙂

Probably one for @totahuanocotl!

@totahuanocotl
Copy link
Contributor

totahuanocotl commented Aug 21, 2019

Hey @markdanko,
I'm very pleased to see that this has worked out for you well!
I'm afraid I don't remember what the state of the branch is, I think I left it as a draft, or an initial attempt since we did not end up going up that road.
I assume it has worked well for you, so I can come back and revisit it because I remember I wanted to try things a bit differently. If you are happy to wait for a couple of weeks (I'm a bit busy at the moment) I can do that for you.

Have you made any changes/improvements on your own to make it work that I should consider when working on it, or are you just using it as is?

@markdanko
Copy link
Author

@totahuanocotl, A few weeks would be cool. The only change I made to that branch was back port' ing the changes in 1.5.0 about /healthz to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants