Forum Discussion
Russell Meyer
Nov 14, 2017Brass Contributor
Unable to grant O365 users access to Tech Community
Has any one ran into issues authorizing Tech Community with federated IDs? If I log in with a GA, gives me some warnings about access, etc...if I accept, the account I good but others in the tenant, ...
Russell Meyer
Nov 15, 2017Brass Contributor
its set to no...even flipped to yes and assigned, no love
VasilMichev
Nov 15, 2017MVP
Switch it to No, try accessing the MTC with your admin account and consent to the app. If no consent prompt appears, try triggering it manually via this link:
https://login.microsoftonline.com/common/adminconsent/?client_id=09213cdc-9f30-4e82-aa6f-9b6e8d82dab3&redirect_uri=https%3A%2F%2Ftechcommunity.microsoft.com%2Fauth%2Foauth2callback&response_type=code&state=https%3A%2F%2Ftechcommunity.microsoft.com%2F&scope=User.Read+openid+email+profile+offline_access
The "adminconsent" part makes sure that it will trigger the correct flow.
And a disclaimer to never click such links without double and triple-checking to what you are consenting :)
- Russell MeyerNov 15, 2017Brass Contributormost of that URL makes sense and I had it about 90% there but kept getting errors, but the client ID, where is that derived from?
- Russell MeyerNov 15, 2017Brass Contributorso basically take replace "common/oauth2/v2.0/authorize" with "common/adminconsent" that is provided in URL for login...
- VasilMichevNov 15, 2017MVP
Yup, replace the endpoint. The ClientID is the identifier of the application - you can compare it against what you are seeing in the Azure AD portal for the MS Tech Comm app.
Again, pay attention to what you are consenting, as there have been some baddies exploiting this already :)