In order for apps and services to be able to authenticate users and authorize client access via (public) HTTP, the best protocol to choose seems to be OpenID Connect.
@thisismissem has proposed this feature and suggested that Doorkeeper would be the easiest way of adding it. There's a Doorkeeper extension for OIDC, which is used by GitLab and Siemens apparently, so I would expect it to be safe.
In order for apps and services to be able to authenticate users and authorize client access via (public) HTTP, the best protocol to choose seems to be [OpenID Connect](https://openid.net/developers/how-connect-works/).
[@thisismissem](https://github.com/thisismissem) has proposed this feature and suggested that [Doorkeeper](https://github.com/doorkeeper-gem/doorkeeper) would be the easiest way of adding it. There's a Doorkeeper [extension for OIDC](https://github.com/doorkeeper-gem/doorkeeper-openid_connect), which is used by GitLab and Siemens apparently, so I would expect it to be safe.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In order for apps and services to be able to authenticate users and authorize client access via (public) HTTP, the best protocol to choose seems to be OpenID Connect.
@thisismissem has proposed this feature and suggested that Doorkeeper would be the easiest way of adding it. There's a Doorkeeper extension for OIDC, which is used by GitLab and Siemens apparently, so I would expect it to be safe.
Support OpenID Connectto Add OpenID Connect