We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The authorize and token urls need to be customisable to include a tenant name, to support single-tenant app registration
omniauth-bn-office365/lib/omniauth/strategies/office365.rb
Line 18 in 258b3ef
https://stackoverflow.com/questions/53526121/use-a-tenant-specific-endpoint-or-configure-the-application-to-be-multi-tenant
The text was updated successfully, but these errors were encountered:
https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-v2-protocols#endpoints
Sorry, something went wrong.
This is pretty critical for me too, without this a user from any office365 tenant can authenticate.
You need to adapt lines 18 and 19:
authorize_url: '/common/oauth2/v2.0/authorize', token_url: '/common/oauth2/v2.0/token'
to something like this:
authorize_url: '/mytenant/oauth2/v2.0/authorize token_url: '/mytenant/oauth2/v2.0/token
We forked your repo to https://github.com/werk21/omniauth-bn-office365/ and added this feature. Just set OFFICE365_TENANT in ENV.
No branches or pull requests
The authorize and token urls need to be customisable to include a tenant name, to support single-tenant app registration
omniauth-bn-office365/lib/omniauth/strategies/office365.rb
Line 18 in 258b3ef
https://stackoverflow.com/questions/53526121/use-a-tenant-specific-endpoint-or-configure-the-application-to-be-multi-tenant
The text was updated successfully, but these errors were encountered: