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:
- main URLs: https://openqa.fedoraproject.org and https://openqa.stg.fedoraproject.org
- contacts: @adamwill / qa-tools-sig
- privacy: standard Fedora privacy policy

Some more OIDC specific information then:
- redirect URI: https://open.qa/docs/#_oauth2 says "Use …/login as callback URL" - I guess that's https://openqa.fedoraproject.org/login or https://openqa.stg.fedoraproject.org/login
- Does the application need the user names, or will an application-specific pseudonym suffice?
- I'm not totally sure. The code is https://github.com/os-autoinst/openQA/blob/master/lib/OpenQA/WebAPI/Auth/OAuth2.pm . It looks like the oauth2 properties it uses to get the 'id' and 'nickname' are configurable. In the existing user data as shown in the web UI, usernames (which I guess are the same as the 'id' we're getting here) are e.g. http://adamwill.id.fedoraproject.org/ and nicknames are the FAS username e.g. adamwill. so...we need the oauth2 data to contain a field which is http://(fasname).id.fedoraproject.org and a field which is just (fasname), I guess. Failing that, we'll have to gin up an openQA db query to change all the existing usernames, or I can patch openQA to have an ipsilon path which constructs the correct username/id from the FAS name, or something.
- Which authorization flow does the application use?
- Not sure. The module we're using is https://metacpan.org/pod/Mojolicious::Plugin::OAuth2 , from https://github.com/marcusramberg/Mojolicious-Plugin-OAuth2/blob/0312b87eb49d69fe3587ed58aff61378864684e5/lib/Mojolicious/Plugin/OAuth2.pm#L164 it looks like it's authorization_code .
- Which token authentication method does the application use?
- Not sure. A mock config presumably used in the tests at https://github.com/marcusramberg/Mojolicious-Plugin-OAuth2/blob/0312b87eb49d69fe3587ed58aff61378864684e5/lib/Mojolicious/Plugin/OAuth2/Mock.pm#L227 says token_endpoint_auth_methods_supported":["client_secret_post","private_key_jwt","client_secret_basic"]
- Which response type does the application rely on?
- I think it'll be code .

Sorry for the lack of certainty on some points. I think we may actually need to patch openQA a bit to make it possible to use Mojolicious-Plugin-OAuth2's OpenIDC 'mode', but I can probably handle that.