opensafely-core / opensafely-core/reports
Next stage NHS ID development
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 5
Description
Initial POC (#1) is complete; login with NHS Identity's OIDC flow and test user credentials on the simple OIDC realm works. The next stage is to progress to testing on the dev Healthcare realm, which requires authentication via smartcard or alternative
see Ways to authenticate
The above link is not entirely clear, but most of the methods require an N3 connection. The smartcard plugin is a custom one that needs to be provided by NHS ID, and also required the N3 connection. The method that will probably work for us for testing is a windows device + hardware key.
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.
Research direction
Review the completed initial POC in issue #1 and the linked NHS Ways to authenticate guidance first. Determine which authentication method is available for the dev Healthcare realm, including the stated Windows device and hardware-key option. Done means testing the NHS Identity OIDC flow successfully against that realm.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100