#7321 Register taigastg with Ipsilon in staging
Closed: Fixed 3 years ago Opened 3 years ago by abompard.

  • Describe what you need us to do:
    I would like a client_id and a client_secret for the staging instance of Taiga. Ideally these would be available in ansible as taiga_stg_oidc_client_id and taiga_stg_oidc_client_secret.
    The callback URL is https://taigastg.fedorainfracloud.org/api/oidc/callback/.

  • When do you need this?
    When you can.

  • When is this no longer needed or useful?
    When we stop using Taiga

  • If we cannot complete your request, what is the impact?
    I can't test the OIDC auth plugin for Taiga and we can't move forward with using Taiga.


Metadata Update from @cverna:
- Issue tagged with: authentication

3 years ago

Metadata Update from @puiterwijk:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Apparently the ansible variable taiga_stg_oidc_client_id contains taiga-stg, is that intended? I was expecting a long UUID-like string.

Metadata Update from @abompard:
- Issue status updated to: Open (was: Closed)

3 years ago

@abompard For manually registered clients, we use descriptive client IDs, so this is correct :).
Thanks for confirming!

Metadata Update from @puiterwijk:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

According to puiterwijk, that's perfectly normal. Closing again.

Login to comment on this ticket.

Metadata