How to use the new branch feature with docker development environment

@anon16419211 no it’s not. I still need the FOREST_CLIENT_ID . Here are the logs when I remove it:

api_forest_1  | [forest] 🌳🌳🌳  Unable to register the client
api_forest_1  | {
api_forest_1  |   "configuration": {
api_forest_1  |     "authorization_endpoint": "https://api.forestadmin.com/oidc/auth",
api_forest_1  |     "device_authorization_endpoint": "https://api.forestadmin.com/oidc/device/auth",
api_forest_1  |     "claims_parameter_supported": false,
api_forest_1  |     "claims_supported": [
api_forest_1  |       "sub",
api_forest_1  |       "email",
api_forest_1  |       "sid",
api_forest_1  |       "auth_time",
api_forest_1  |       "iss"
api_forest_1  |     ],
api_forest_1  |     "code_challenge_methods_supported": [
api_forest_1  |       "S256"
api_forest_1  |     ],
api_forest_1  |     "end_session_endpoint": "https://api.forestadmin.com/oidc/session/end",
api_forest_1  |     "grant_types_supported": [
api_forest_1  |       "authorization_code",
api_forest_1  |       "urn:ietf:params:oauth:grant-type:device_code"
api_forest_1  |     ],
api_forest_1  |     "id_token_signing_alg_values_supported": [
api_forest_1  |       "HS256",
api_forest_1  |       "RS256"
api_forest_1  |     ],
api_forest_1  |     "issuer": "https://api.forestadmin.com",
api_forest_1  |     "jwks_uri": "https://api.forestadmin.com/oidc/jwks",
api_forest_1  |     "registration_endpoint": "https://api.forestadmin.com/oidc/reg",
api_forest_1  |     "response_modes_supported": [
api_forest_1  |       "query"
api_forest_1  |     ],
api_forest_1  |     "response_types_supported": [
api_forest_1  |       "code",
api_forest_1  |       "none"
api_forest_1  |     ],
api_forest_1  |     "scopes_supported": [
api_forest_1  |       "openid",
api_forest_1  |       "email",
api_forest_1  |       "profile"
api_forest_1  |     ],
api_forest_1  |     "subject_types_supported": [
api_forest_1  |       "public"
api_forest_1  |     ],
api_forest_1  |     "token_endpoint_auth_methods_supported": [
api_forest_1  |       "none"
api_forest_1  |     ],
api_forest_1  |     "token_endpoint_auth_signing_alg_values_supported": [],
api_forest_1  |     "token_endpoint": "https://api.forestadmin.com/oidc/token",
api_forest_1  |     "request_object_signing_alg_values_supported": [
api_forest_1  |       "HS256",
api_forest_1  |       "RS256"
api_forest_1  |     ],
api_forest_1  |     "request_parameter_supported": false,
api_forest_1  |     "request_uri_parameter_supported": true,
api_forest_1  |     "require_request_uri_registration": true,
api_forest_1  |     "claim_types_supported": [
api_forest_1  |       "normal"
api_forest_1  |     ]
api_forest_1  |   },
api_forest_1  |   "registration": {
api_forest_1  |     "redirect_uris": [
api_forest_1  |       "https://api-forest.dev.localhost/forest/authentication/callback"
api_forest_1  |     ],
api_forest_1  |     "token_endpoint_auth_method": "none"
api_forest_1  |   },
api_forest_1  |   "error": {
api_forest_1  |     "error": "unauthorized_client",
api_forest_1  |     "error_description": "Web clients must be authenticated"
api_forest_1  |   }
api_forest_1  | }
api_forest_1  | info:    ┏ POST /forest/authentication 400 557ms +21s
api_forest_1  | info:    ┃ [ 1] {
api_forest_1  | info:    ┃ [ 2]   http: {
api_forest_1  | info:    ┃ [ 3]     request: {
api_forest_1  | info:    ┃ [ 4]       method: 'POST',
api_forest_1  | info:    ┃ [ 5]       url: 'http://api-forest.dev.localhost/forest/authentication',
api_forest_1  | info:    ┃ [ 6]       path: '/forest/authentication',
api_forest_1  | info:    ┃ [ 7]       query: {},
api_forest_1  | info:    ┃ [ 8]       headers: {},
api_forest_1  | info:    ┃ [ 9]       source_ip: '172.23.0.1'
api_forest_1  | info:    ┃ [10]     },
api_forest_1  | info:    ┃ [11]     responseTime: 557,
api_forest_1  | info:    ┃ [12]     response: { status: 400, message: 'Bad Request', type: 'application/json; charset=utf-8', headers: {} }
api_forest_1  | info:    ┃ [13]   },
api_forest_1  | info:    ┃ [14]   service: 'api_forest',
api_forest_1  | info:    ┃ [15]   env: 'development',
api_forest_1  | info:    ┃ [16]   version: 'v2.0.4-34-g5b62b76d',
api_forest_1  | info:    ┃ [17]   context: { message: 'POST /forest/authentication 400 557ms' },
api_forest_1  | info:    ┃ [18]   timestamp: '2021-06-29T09:02:43.842Z'
api_forest_1  | info:    β”— [19] }

The FOREST_CLIENT_ID will be needed on your other environment but as long as you are in a development environment this is not needed.

Again, this new authentication mechanism from the v7 involves upgrading other environments to v7. :slight_smile: Once you’ve done that if the authentication issue is still there we will scheduled a call to debug you.

@anon16419211 yes but I want to test it on non prod env before migrating V7 on prod

Oh I understand, so I have one more question, do you have authentication issue about anything other than forest branch commands?

@anon16419211 yes I do. I have deploy the V7 on my dev, integration and staging environments and I cannot connect anymore to Forest UI on integration and staging. FOREST_CLIENT_ID and APPLICATION_URL are deployed on all environment.

We are deploying V7 to prod to see if it’s better with the V7 on all environement.

I may need a call quickly (sorry) to debug the connection and have Forest up in prod.

@anon16419211 we have deployed V7 on all environment and we can’t connect to Forest UI anymore. Shall we have a call ?