sameersbn / sameersbn/docker-gitlab
CAS3 attribute mapping
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Using OAUTH_CAS3_* environment variables it seems I can configure gitlab to use my CAS3 server.
The problem is that my CAS3 server sends specific attributes names, and there is no OAUTH_CAS3 environment variable I can use to map those fields.
I want to use uid_field, name_key, nickname_key, first_name_key and last_name_key of http://www.rubydoc.info/gems/omniauth-cas3/1.1.2#Optional, could you create new OAUTH_CAS3 environment variables to fit this need?
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.
Research direction
Start by tracing the existing OAUTH_CAS3 environment-variable handling and compare it with the uid_field, name_key, nickname_key, first_name_key, and last_name_key options documented for omniauth-cas3. Done means each requested attribute mapping can be configured through an OAUTH_CAS3 variable and is passed to the CAS3 integration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, gitlab, shell
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100