Martin Collado
Martin Collado
Maybe would be a good idea to have different systems? One implemented with a check-in system, and another pulling data from intranet networks. Check-in system: Could give the control to...
Exactly! I'm trying to use the Gitlab OAuth2 Provider (https://docs.gitlab.com/ee/api/oauth2.html). I'll try with a subclass as you mention. PS: btw, which oauth2 flow are you using por this library or...
Finally I used as you say an a subclass like this ```python class GitlabServiceOAuth2(OAuth2): async def get_id_email(self, token: str) -> Tuple[str, str]: async with httpx.AsyncClient() as client: response = await...
Sure, Gitlab - Onpremise 13.0 (Omnibus) Calling the /authorize with: - **authentication_backend**: jwt - **scopes**: openid Response provided by Gitlab with the **/authorize** call: ```json { "access_token":"fab35f152d12c5008b14e9ff7e6c1c6a9f2093c896489e7466d2a1f7429bdf47", "token_type":"Bearer", "refresh_token":"d2423db64df0db58087d4e869848bd2ab8fccb4cf1fcea1702afbe364f6893ee", "scope":"openid",...
For the requests you need to send the `access_token`, but for the user information you need to call the `/userinfo` endpoint (https://docs.gitlab.com/ee/integration/openid_connect_provider.html). The `ìd_token` is given for the OpenID scope....
Sure!! **Backend**: jwt **Scope**: profile ```json { "access_token":"e260271eaf04057dd31ed7450cc15f75356e6fbf7c2fbb9a00d6ef549d4cfe70", "token_type":"Bearer", "refresh_token":"133831ac254da522ee2519c627a7fe708dc7cebb8db6392c6311d492b972a632", "scope":"profile", "created_at":1590678706 } ``` Scopes on Gitlab: 
What I pasted here was exactly that (I've had overwrite the entire class to investigate on the response from the server like you): **Backend**: jwt **Scope**: profile ```json { "access_token":"e260271eaf04057dd31ed7450cc15f75356e6fbf7c2fbb9a00d6ef549d4cfe70",...
Actually, what stopped to me was this: (I started with authlib and later on I changed it by httpx-oauth) > Hi @martincolladofab! I deliberately put `authlib` aside because of its...
Yes sure, just I though that would be nice to handle a little more of the OAuth and authorizations flows inside the library to complement the basic of the OAuth...
To add more about it, it would be nice to have support for the hypertable creation and maybe for more like this: ```yaml apiVersion: schemas.schemahero.io/v1alpha4 kind: Table metadata: name: users...