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

Add new microsoft_v2_auth provider for devise #24600

Merged
merged 1 commit into from Aug 31, 2018

Conversation

maddiedierker
Copy link
Contributor

@maddiedierker maddiedierker commented Aug 31, 2018

This adds the omniauth-microsoft_v2_auth gem in order to authenticate all Microsoft account types, since our current gem (omniauth-windowslive) does not work for Officer 365 users.

I chose this gem for a few reasons: 1) it works directly based off of Microsoft's suggested setup for Rails apps, and 2) I couldn't find any other gems that used the AAD 2.0 endpoint that we need to use for this integration.

There is a lot of follow-up needed to actually get SSO and silent takeover working for existing windowslive users and new MSFT SSO users, but I wanted to get the gem/Devise setup in first to make sure all goes well.

Unfortunately, it looks like I can't test this functionality locally because Microsoft requires the redirect URI to be HTTPS and our localhost uses HTTP:
screen shot 2018-08-31 at 9 51 46 am

@@ -1029,4 +1037,4 @@ RUBY VERSION
ruby 2.5.0p0

BUNDLED WITH
1.16.1
1.16.2
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it expected that we're bumping the patch version? Probably not an issue, just double-checking.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this was not intentional, so i'm not sure why the version was bumped. my local version is 1.16.2, so maybe when i added the new gem and bundled, it bumped the version?

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

Successfully merging this pull request may close these issues.

None yet

3 participants