-
Shortcut API Key and Google Auth token should be received in tandem which then retrieves the Google user ID associated with the response. Values should be encrypted and then stored in the database
-
# Story
Currently, WillowSword is unprotected and allows anyone to deposit. We must implement authorization before rolling this feature out.
https://github.com/CottageLabs/willow_sword/wiki/Enablin…
-
-
add authorization system to the system, user should register first, the credentials should be stored in database, the registered user can login
-
**Problem description**
ICM gave guidelines to API subprojects and provided the text below which mentions OAuth2 Authorization Code grant instead of OIDC Authorization Code flow.
[number_verificat…
-
### The problem
Tuya app gives an error
QR expired. Refresh it and scan again.
I have reloaded the integration but QR code is not updated
### What version of Home Assistant Core has the iss…
-
**1. Request**
- Login: Make a POST request to **/auth/login** with user credentials.(username, password)
- Registration: Make a POST request to **/auth/register** to create a new user. (username, p…
-
Hey! Thanks for the awesome adapter. I almost managed to make it work for my case, but encountered the following error while authorizing using SSO:
I run:
```
harlequin -a adbc "somename.snowflak…
-
# Roles
- Caller
- Member
- Admin
- Owner
A header auth claim?:
1. Workspaces need to be able to use email to invite people to make an account as a 'Caller'
2. Campaigns need to be able to be…
-
## Summary
In moving away from LDAP , theres need to adjust the current Gerrit flow and fetch the CLA status of a given LFID user
## User Story
- As a project administrator, I want to verify if a …