```{ "data": { "type": "access-tokens", "attributes": { "username": "

U03SN9552JC

{
  "data": {
    "type": "access-tokens",
    "attributes": {
      "username": "<mailto:admin@spryker.com|admin@spryker.com>",
      "password": "change123"
    }
  }
}

Unknown

try with <mailto:sonia@spryker.com|sonia@spryker.com>

U03SN9552JC

Still failed unfortunately

Unknown

what is the URL?

U03SN9552JC

So through postman, I'm just doing

{{ENDPOINT_URL}}/access-tokens

U03SN9552JC

It seems to hit the endpoint

Unknown

What is the {{ENDPOINT_URL}} ?

U03SN9552JC

<http://glue.pricecoshop.local/>

U03SN9552JC

Its just something we changed from http://glue.de.spryker.local/ in the config

Unknown

so you are not missing de ?? or the equivalent in your config

U03SN9552JC

I'll try this on a fresh B2C real quick to see if thats the problem

Unknown

For reference
https://docs.spryker.com/docs/pbc/all/identity-access-management/202212.0/manage-using-glue-api/glue-api-authenticate-as-a-customer.html#request

U03SN9552JC

Mohammed, it seems I can authenticate Sonia on the B2C and not our own

giovanni.piemontese

Do u use docker/sdk? If yves, it can be possible that the oauth secret generated via docker/sdk matches not more with its one saved in db..

U03SN9552JC

I can check via password_check agains the hash, I'll do that now

U03SN9552JC

Yeah we use the docker/sdk

Unknown

I think you missing with store subdomain within your configured URL
as you will see in the B2C with sonia successfully authenticated the URL contained de

U03SN9552JC

            glue_eu:
                application: glue
                endpoints:
                    glue.pricecoshop.local:
                        store: DE

U03SN9552JC

This is the deploy.dev.yml endpoint for this

giovanni.piemontese

it is the secret! i send u a workround to get this working again.. or just can just run docker/sdk up --build --data and the spy_oauth_client::secret is again saved with actual Env value generated from docker/sdk

U03SN9552JC

I'll try the docker command real quick

giovanni.piemontese

ok

giovanni.piemontese

otherwise

• docker/sdk cli
• echo $SPRYKER_OAUTH_CLIENT_SECRET
• generate secret with password_hash bcrypt and save in spy_oauth_client -> secret

U03SN9552JC

@UL65CH0MC winner winner!

U03SN9552JC

I ran that command

U03SN9552JC

And now I can auth

U03SN9552JC

I see that I can only auth users with email addresses that are validated. Can I change a value somewhere, I'm using <mailto:example@example.com|example@example.com> so the email technically goes nowhere

giovanni.piemontese

good! the secret is only saved on init-db command performed one time on docker/sdk up...

when u run another day just docker/sdk up the secret does not match more with its one in db...

what do u mean with:
Can I change a value somewhere, I'm using <mailto:example@example.com|example@example.com> so the email technically goes nowhere

U03SN9552JC

in the docs it says

U03SN9552JC

If you are authenticating as a newly created customer, make sure to verify your email address first. If an email address was not confirmed, the endpoint returns the 403 "Failed to authenticate user" error.

U03SN9552JC

So I created a new customer using glue