bcgov / bcgov/parks-data-register
[L] Auth/ID Option Analysis
- Dominant language
- JavaScript
- Stars
- 5
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
This ticket is to do a deep dive into authentication options out there that could potentially be used in future products and tools. It is meant to inform decision-making, but will not result in a decision.
Conduct an options analysis that looks at different authentication and identity options, how they work and integrate into other tools, and effort to implement. Specifically look at what identity options exist, how they can be incorporated, and where are they offered (specify if BC Gov or not). Also investigate authentication options and specifically look at how different options affect things like permissions and roles, integration into existing and future tools, scalability (100 users versus 1 million), volume, etc.
**Acceptance Criteria:**
- develop a list of options
- Pros/Cons
- POC / examples of use
- identify risks
- identify costs ($, effort, time, reliability, maintenance, etc.)
- documentation on all above will be in Teams folder: [Dev Channel - 5. Research and Innovation - Auth and ID](https://bcgov.sharepoint.com/:f:/r/teams/08548-DevChannelNew/Shared%20Documents/Dev%20Chat/5.%20Research%20and%20Innovation/Auth%20%26%20ID?csf=1&web=1&e=nkhPt7)
## Notes
- some of this analysis might be internal/confidential so use teams for documentation, not this issue
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.