Closed cmeessen closed 5 months ago
Waiting for #1103 to be closed by @ewan-escience
It is also good to note that when ORCID login is disabled and ORCID coupling is enabled, when an ORCID is coupled, this ORCID is still added to the login allow list.
It is also good to note that when ORCID login is disabled and ORCID coupling is enabled, when an ORCID is coupled, this ORCID is still added to the login allow list.
I added a warning about this into the documentation, and also split it up into sections for common variables, coupling and authentication respectively. Could you please double check whether all common variables are mentioned correctly?
Could you please double check whether all common variables are mentioned correctly?
Everything seems to be there. You used as exampleORCID_REDIRECT_COUPLE=http://YOUR-RSD-DOMAIN/auth/couple/orcid
, maybe you can also use YOUR-RSD-DOMAIN
for ORCID_REDIRECT
.
Issues
0 New issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
Issues
0 New issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
You used as example ORCID_REDIRECT_COUPLE=http://YOUR-RSD-DOMAIN/auth/couple/orcid, maybe you can also use YOUR-RSD-DOMAIN for ORCID_REDIRECT.
I replaced it with the same values as in .env.example
to be consistent here, and added a note at the top of the document to replace localhost
with the corresponding RSD domain.
Distinguish between login and coupling auth providers
Fixes #1095 #1097
Changes proposed in this pull request:
RSD_AUTH_COUPLE_PROVIDERS
How to test:
.env
, set:docker compose build --parallel && docker compose up --scale scrapers=0
docker compose down
ORCID
toRSD_AUTH_PROVIDERS
and repeat previous steps. Verify that ORCID login worksdocker compose down
.env
, comment outRSD_AUTH_COUPLE_PROVIDERS
, or set it to something else thanORCID
PR Checklist:
docker-compose.yml