Clarify use of secret in Microsoft Entra authentication docs
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 55/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- authentication, documentation
Research direction
Open the Microsoft Entra authentication tutorial and read the “Configure your secrets” section, especially step 4 and the paragraph that follows. Clarify the server_metadata_url example and its account-scope guidance so readers know what value to supply; done when the snippet and surrounding explanation cannot be mistaken for a universal default.
Written by the indexing model from the issue text.
Description
Link to doc page in question (if any): https://docs.streamlit.io/develop/tutorials/authentication/microsoft
Name of the Streamlit feature whose docs need improvement: Authentication using Microsoft Entra
What you think the docs should say: This is a really great tutorial but there's one area where I think people might go wrong if they're not paying attention, which would be worth clarifying.
Under Configure your secrets, step 4, the code snippet includes server_metadata_url = "https://login.microsoftonline.com/consumers/v2.0/.well-known/openid-configuration". This would be clearer as server_metadata_url = "xxx".
The paragraph of text that follows states that server_metadata_url is a string that the user needs to supply, but is easy to miss. The string used in the code snippet only works if people allow access to the app using personal Microsoft accounts ('consumers').
- Dominant language
- JavaScript
- Stars
- 178
- Forks
- 705
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 39
Contributor guide
No contributing guide indexed for this repository
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 streamlit/docs
-
docs needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
docs needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
docs
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
docs needs triage
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100