ukayani / auth0-deploy Goto Github PK
View Code? Open in Web Editor NEWA tool for automated deployment of auth0 components
License: MIT License
A tool for automated deployment of auth0 components
License: MIT License
Using the following config.json
{
"allowed_clients": null,
"allowed_logout_urls": null,
"allowed_origins": null,
"callback_url_template": false,
"callbacks": null,
"client_id": "xbdof-iI9cCpXmt_0pP6PbBa6zzhQSI1",
"config_route": null,
"custom_login_page_on": false,
"global": false,
"grant_types": [
"implicit",
"authorization_code",
"client_credentials",
"refresh_token"
],
"is_first_party": true,
"jwt_configuration": {
"lifetime_in_seconds": "36000",
"secret_encoded": false
},
"name": "Default App",
"tenant": "bamboo"
}```
When trying to do a deploy for the Default App, we are getting validation errors:
```bash
xf186001@MUSXF186001-209:~/workplace/bamboo-config/components » auth0-deploy client Default\ App -c {client_id} -s {client_secret} -d bamboo.auth0.com 1 ↵
Updating client: Default App
Payload validation error: 'Additional properties not allowed: tenant,global,config_route,client_id,callback_url_template'.
xf186001@MUSXF186001-209:~/workplace/bamboo-config/components » auth0-deploy client Default\ App -c {client_id} -s {client_secret} -d bamboo.auth0.com 1 ↵
Updating client: Default App
Payload validation error: 'Expected type array but found type null' on property callbacks (A set of URLs that are valid to call back from Auth0 when authenticating users). (also) Payload validation error: 'Expected type array but found type null' on property allowed_origins (A set of URLs that represents valid origins for CORS). (also) Payload validation error: 'Expected type array but found type null' on property allowed_logout_urls (A set of URLs that are valid to redirect to after logout from Auth0). (also) Payload validation error: 'Expected type array but found type null' on property allowed_clients (Ids of clients that will be allowed to perform delegation requests. Clients that will be allowed to make delegation request. By default, all your clients will be allowed. This field allows you to specify specific clients). (also) Payload validation error: 'Additional properties not allowed: secret_encoded' on property jwt_configuration (An object that holds settings related to how JWTs are created).
From @xiananfan
I first removed the "tenant,global,config_route,client_id,callback_url_template" fields from the config.json. Then I encounter the validation error above.
So it seems the tool is complaining the missing fields "callbacks", "allowed_origins", "allowed_logout_urls", "allowed_clients". Add additional field inside the "jwt_configuration" object.
I could provide the above fields in a real client. However, if you notice, I was trying to update the "Default App" client, which was there by default when you create a new tenant in auth0. I was wondering if you could consider allowing the value to not be there as well. Because the value is a direct dump from the management api v2. In other words, missing the value should be valid, and not encounter a validation error.
Would it be possible to have some more info, or even an examples folder with a few usage patterns?
I couldn't solve/confirm these questions on submitting connections:
google-oauth2
.Hey,
I work for Auth0 and am trying to get in contact with you. Is there some way I can contact you?
Hi @ukayani,
We spoke a long while back about merging auth0-deploy with auth0-deploy-cli.
We have finally rewritten auth0-deploy-cli to support most objects within Auth0.
I believe this project is no longer maintained. May I suggest a link to auth0-deploy-cli in your readme.md?
Hey @ukayani,
Is this meant to also dump the auth0 config/components as a starting point?
I am trying to deploy the clients configurations. Followed the basic setup to setup the repository:
clients
All Applications
config.json
API Explorer Client
config.json
grants.json
auth0-deploy-cli-extension
config.json
grants.json
auth0-github-deploy
config.json
grants.json
Default App
config.json
With the above folder structure, when use the following command:
auth0-deploy client -c <client-id> -s <client-secret-id> -d <domain.auth0.com>
I got the following message:
Path must be a string. Received undefined.
While updating the existing user's profile, API expecting a password. I don't have any idea why a password is required. Can anyone please advise?
URL: {autho url}/api/v2/users/{user id}
error as follows: {"statusCode":400,"error":"Bad Request","message":"Payload validation error: 'Expected type string but found type null' on property password (New password for this user (mandatory for non-SMS connections)).","errorCode":"invalid_body"}
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.