A modern authorization server built to authenticate your users and protect your APIs
nvl login is still able to list the anvil instances. Where are they stored?
nv add user and a custom json but since nv is deprecated, I'm looking for a new solution.nvl but the fields are restricted (name, given name, etc.) and we can no longer pass a custom json. Should I use the API instead? There does not seem to be any documentation about it yet? Suggestions?
hi there, making good progress on our Anvil install, now getting it working with our PHP Laravel app..
I have tried to create a client with “id_token and token” but getting some error, maybe a combination of some other setting perhaps. Any Ideas??
? Will this be a trusted client? Yes
? Enter a name Coin ID Test 2
? Enter a URI http://test.coinid.com
? Enter a logo URI http://test.coinid.com/assets/images/CoinID.png
? Choose an application type web
? Select response types code id_token token
? Select grant types authorization_code, implicit
? Set the default max age (in seconds) 3600
? Define redirect URIs http://test.coinid.com/login
? Define redirect URIs
? Define post logout redirect URIs http://test.coinid.com/logout
? Define post logout redirect URIs
{ [StatusCodeError: 400 - [object Object]]
name: 'StatusCodeError',
statusCode: 400,
message: '400 - [object Object]',
@RhinoLoft This is the part of the documentation about response_types and grant_types : https://github.com/anvilresearch/connect-docs/blob/master/clients.md#response-types
You might want to try a simpler version with response_types: id_token token and grant_types: implicit
nvl user:register you could probably get away with setting up a shell script that takes JSON, builds the relevant command and runs it
nvl init creates the a views folder, and my understanding was that if the requested view wasn't in that folder, Connect defaults to looking for them in node_modules/anvil-connect/views. Is this correct, or am a misremembering?
/v1/users[/:id]
~/.nvl/sessions/ISSUER should work (if it hasn’t expired)
—json flag to each API command
response_type selection was [“code id_token token”] vs [“code”, “id_token token”]
code, id_token token, and code id_token token, each of which are distinct response types
This URI MUST exactly match one of the Redirection URI values for the Client pre-registered at the OpenID Provider, with the matching performed as described in Section 6.2.1 of [RFC3986] (Simple String Comparison). When using this flow, the Redirection URI SHOULD use the https scheme; however, it MAY use the http scheme, provided that the Client Type is confidential, as defined in Section 2.1 of OAuth 2.0, and provided the OP allows the use of http Redirection URIs in this case. The Redirection URI MAY use an alternate scheme, such as one that is intended to identify a callback into a native application.
/callback you may use /cb), but a host whitelist may make sense.
code id_token token one
code id_token token issue
code id_token token and that not working and I believe it got fixed by selecting everything through nvl
@simonrenoult thanks, i am working thru this and experimenting, seems some issue with the cli, if i try this
ubuntu@ip-172-10-0-172:~$ nvl client:register --name Coin ID Test 2 --uri http://test.coinid.com --logo-uri http://test.coinid.com/assets/images/CoinID.png --application-type web --response-type code --grant-type authorization_code --default-max-age 3600
Selected issuer test.coinid.com (https://testanvil.coinid.com)
? Will this be a trusted client? Yes
? Define redirect URIs http://test.coinid.com/login
? Define redirect URIs
? Define post logout redirect URIs
{
it works, if i try this (and put the redirect-uri on command line) it fails
ubuntu@ip-172-10-0-172:~$ nvl client:register --name Coin ID Test 2 --uri http://test.coinid.com --logo-uri http://test.coinid.com/assets/images/CoinID.png --application-type web --response-type code --grant-type authorization_code --default-max-age 3600 --redirect-uri http://test.coinid.com/login
Selected issuer test.coinid.com (https://testanvil.coinid.com)
? Will this be a trusted client? Yes
? Define post logout redirect URIs
{ [StatusCodeError: 400 - [object Object]]