Startup configuration for Authentication and Authorization
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- android, java
- Domain
- authentication, authorization, documentation, mobile
Research direction
The issue mentions the startup configuration, an Android client, Postman, AD B2C, bearer tokens, and a 401 response. Start by comparing the sample's documented authentication flow with the requested non-Graph API scenario; done means adding clear configuration guidance for the web app and Android-accessed endpoints.
Written by the indexing model from the issue text.
Description
Please provide us with the following information:
This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
Minimal steps to reproduce
I am unable to replicate this sample with an android application communicating with other end points that are not Microsoft Graph. I am successfully authenticating and generating both an id_token with the correct scope captured in the scp claim and an access token as well being used as a bearer token. I keep getting a 401 error both on my android app and postman. I am suspecting that it has to do with how I have setup the authentication and authorization in my startup file. Please provide some guidance with the scenario where my web application which users logon directly through AD B2C and also has end points which can been accessed by the android application after a user logons on and generates a bearer token based on the same logic documented here
Any log messages given by the failure
Expected/desired behavior
OS and Version?
Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Versions
Mention any other details that might be useful
Thanks! We'll be in touch soon.
- Dominant language
- Java
- Stars
- 34
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure-Samples/ms-identity-android-java
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Azure-Samples/ms-identity-android-java#57 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
ADAL packages Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
All issues in Azure-Samples/ms-identity-android-java
Similar issues
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
apache/flink-agents#1156 ·
-
[source-shopify] FAILED bulk operation without partialDataUrl is silently treated as successful Openarea/connectors autoteam community connectors/source/shopify needs-triage team/use type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100