46 lines
2 KiB
YAML
46 lines
2 KiB
YAML
name: OpenID Connect Enrollment
|
|
about: Ticket to coordinate adding a application to our oidc provider
|
|
title: OpenID Connect Enrollment
|
|
labels:
|
|
- needs_review
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
This is to gather needed information for us to onboard your
|
|
application to use the fedoraproject OIDC for authentication.
|
|
- type: textarea
|
|
id: oidc-enroll
|
|
attributes:
|
|
label: oidc-enroll
|
|
description: Fill in your information
|
|
value: |
|
|
To help us register your application in our OIDC service, we need some
|
|
information from you:
|
|
|
|
Note: all the default values provided here are based on the default choice/
|
|
implementation of flask-oidc. If you do not use this library you may have to
|
|
refer to the documentation of your library.
|
|
|
|
Some generic information first:
|
|
- What is the application main URL?
|
|
- Who will be the main contact for the application, or will this be core
|
|
infrastructure?
|
|
- What privacy policy will be applicable to the application, or will this be
|
|
the standard Fedora privacy policy?
|
|
|
|
Some more OIDC specific information then:
|
|
- Which redirect URI(s) will the application use?
|
|
- flask-oidc defaults to: ``<APPLICATION_URL>/oidc_callback``
|
|
but it's configurable (so double-check)
|
|
- Does the application need the user names, or will an application-specific
|
|
pseudonym suffice?
|
|
- ie: using flask-oidc, do you ever rely on ``OIDC.user_getfield('sub')`` to
|
|
get the user's username. If not, this question likely does not matter for
|
|
your application
|
|
- Which authorization flow does the application use?
|
|
- flask-oidc: authorization_code
|
|
- Which token authentication method does the application use?
|
|
- flask-oidc: client_secret_post
|
|
- Which response type does the application rely on?
|
|
- flask-oidc: Code
|