Read the following guideline: Troubleshooting and Support | Squidex. I understand that my support request might get deleted if I do not follow the guideline.
Used code blocks with ``` to format my code examples like JSON or logs properly.
I’m submitting a…
Regression (a behavior that stopped working in a new release)
Bug report
Performance issue
Documentation issue or request
Current behavior
We are a self-hosted environment running in kubernetes/docker. we have configured third party identity as described in the Azure AD (OAuth) with Squidex | Squidex article, configured using Azure AD auth.
We are trying to authenticate the squidex user or to get the squidex auth token using the 3rd party auth token and have not been successful without the users client id/secret combo. This is not a possible solution when we have users on our website UI who will never login to the squidex backend.
We’ve referenced past support tickets such as the below and have so far been unsuccessful
Expected behavior
Users need to be authenticated and authorized using the API.
Squidex users should not be end users. I was thinking about a new feature to build a simple user management, but I have not came to a conclusion yet how it should look like.
If this feature is interesting we can discuss or even have a call.
we have a headless authoring interface, separate from squidex because of the complexity and depth of our content structures. but we still have a need to track users updates through the history log, ideally we could validate an external SSO user and provide a that token for a token exchange with Squidex to authenticate the api.
I have pushed an update. It brings a new user-info field to the schemas. This field has an API key which could be used to authenticate against the Squidex API. So you can create a user schema then.