Client-side only
- Dominant language
- TypeScript
- Stars
- 147
- Forks
- 96
- Avg merge
- 19h 28m
- Merged PRs (30d)
- 87
Description
Hi
Is it possible to use only a client (browser)?
All the examples I've seen so far either rely on creating a temporary token in portal, and/or use some middleware e.g., in nodejs.
I might be misunderstanding something, but
* If I don't want users, could I disable the token-stuff?
* Can I get a token client-side?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the existing examples and the portal-issued temporary-token flow, including the Node.js middleware they use. Done would require a confirmed client-only approach with its token and user-authentication constraints documented, or a clear statement that the service does not support it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, node.js
- Domain
- authentication, cloud, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100