-
Updated
Aug 19, 2021 - Ruby
authentication
Here are 7,515 public repositories matching this topic...
-
Updated
Jul 21, 2021 - PHP
-
Updated
Aug 20, 2021 - Java
-
Updated
Jul 14, 2021 - Ruby
Please update documentation to add Known OIDC Redirect URI's for the following applications:
Wekan (version 5.41) ---> https://wekan.example.com/_oauth_oidc
Portainer CE (version 2.6.1) ---> https://portainer.example.com
Nextcloud (Requires Add-on: Here, Version 22.1.0) --> https://nextcloud.example.com/apps/oidc_login/oidc
-
Updated
Apr 5, 2021 - TypeScript
-
Updated
Aug 16, 2021 - Ruby
-
Updated
Aug 21, 2021 - Go
-
Updated
Aug 20, 2021 - Python
-
Updated
Jul 24, 2021 - JavaScript
-
Updated
Aug 4, 2021 - JavaScript
-
Updated
Aug 18, 2021 - Elixir
-
Updated
Aug 20, 2021 - Objective-C
-
Updated
Aug 6, 2021 - Python
-
Updated
Dec 4, 2020 - JavaScript
-
Updated
Oct 1, 2020 - Java
-
Updated
Jul 15, 2020 - JavaScript
-
Updated
Aug 20, 2021 - SCSS
Is your feature request related to a problem? Please describe.
The public key-based request signing functionality added to sso_proxy in buzzfeed/sso#106 is undocumented. In particular, it's not immediately obvious how to a) generate an appropriate keypair or b) validate a signed request in an upstream service.
Describe the solution you'd like
New documenta
-
Updated
Feb 9, 2021 - C#
-
Updated
May 25, 2021 - PHP
-
Updated
Jul 7, 2021 - Python
-
Updated
Oct 30, 2020 - Shell
Before opening, please confirm:
- I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
- I have searched for duplicate or closed issues.
- I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-cli/blob/master/CONTRIBUTI
Improve this page
Add a description, image, and links to the authentication topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the authentication topic, visit your repo's landing page and select "manage topics."
Description📓
Partially based on this tweet https://twitter.com/t3dotgg/status/1413983193212981248 and closed issues like #969 #497 #525 (and highly probable interest), we should document a way to secure Preview environments.
Given the (unchecked) assumption that most of our users use OAuth as their main provider, the main challenge lies in that Preview environments usually have a dynami