Closed dearlordylord closed 10 months ago
Hail, @Firfi 👋
I've noticed you shared secret values: SECRET
, FIEF_CLIENT_ID
, FIEF_CLIENT_SECRET
, ENCRYPTION_KEY
. Those are highly sensitive and you should keep them secret.
For your security, I've taken the liberty to replace them with dummy values.
Hail, @Firfi 👋 Welcome to Fief's kingdom!
Our team will get back to you very soon to help.
In the meantime, take a minute to star our repository ⭐️
Farewell!
Hail, @Firfi 👋
I've noticed you shared secret values:
SECRET
,FIEF_CLIENT_ID
,FIEF_CLIENT_SECRET
,ENCRYPTION_KEY
. Those are highly sensitive and you should keep them secret.For your security, I've taken the liberty to replace them with dummy values.
they were really all right to share and I was aware, but all right.
network_mode: host
solves the issue but isn't desirable
Describe the bug
https://github.com/fief-dev/fief/blob/6df2773358d536c5385dc89bc0e2741b403675a3/fief/repositories/workspace.py#L24
admin api call cannot identify any domain except the given with ROOT_DOMAIN/FIEF_DOMAIN on setup (i.e. localhost is recognized, but inner docker-compose domains are not)
To Reproduce
docker-compose.yml: (note: env secrets are generated for testing and are not my production secrets)
-> run -> get CANT_DETERMINE_VALID_WORKSPACE error
however, run the same curl command from the host machine with
http://localhost:8000/admin/api/users/
and it finds the workspaceExpected behavior
I expect it to understand default workspace with whatever root domain it's accessed from
Configuration
self-hosted, as per
https://docs.fief.dev/self-hosting/quickstart/
butFIEF_MAIN_ADMIN_API_KEY=ACAB
addedAdditional context
For context, the main point of why I'm doing this call from inside docker-compose is that I'd like to setup some default schema, namely a field for users, that I'd like to do through admin API automatically on docker setup