[ ] Regression (a behavior that stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[x ] Documentation issue or request
Environment
[x ] Self hosted with docker
[ ] Self hosted with IIS
[ ] Self hosted with other version
[ ] Cloud version
Version: 5.0.0
Browser:
[x ] Chrome (desktop)
[ ] Chrome (Android)
[ ] Chrome (iOS)
[ ] Firefox
[ ] Safari (desktop)
[ ] Safari (iOS)
[ ] IE
[ ] Edge
Hi there…
We just started using squidex as a supplement to our solutions, and using it as a content-store and configuration backend, in a server-to-server architecture. We have a webapp as a frontend to our customers that mainly interacts with our own server.
We have some user magnement and Roles in our system to restrict access to different resources in our system depending on the role.
I have read about the identity server in squidex, but as I can see there is no options for us to put custom claims in the JWT that is issued from the identity server. So how should we go about it, if we want to migrate our user magnement and roles to squidex?
you have to distinguish between end users and squidex users. Squidex users are content writers, editors, publishers, admins…everybody who has access to the Management UI.
Squidex identity is basically an identity server which stores all data in Squidex as normal schemas and has a UI based on bootstrap: https://github.com/squidex/squidex-identity
Yeah I’m talking about our end users.
So the process for us would be to host the identity server as a separate app and use that service to manages the end users?
You writing some about that we should edit
Squidex.Identity/appsettings.json
Since we host Squidex as a container, what are the steps here?
I can see Identity Server is deprecated now. Could I still use it or is there any other recommended solution with Squidex now for managing my app users/customers?
Here I mean Squidex Identity. I could make it working with cloud.squidex.io but not with the self hosted local Squidex Server(CMS) app. I changed these settings as per the App in the CMS and by newly creating the apps but not worked and showed multiple issues like http not found/ app, schema, content doesn’t exist/ cannot access token, etc. I could see the identity server working in the Squidex CMS and has the Squidex.Identity_Users documents and all other related documents for the Squidex Identity but not able to connect or run under the self hosted Squidex CMS.
“app”: {
/*
* The url to your squidex server. /
“url”: “https://cloud.squidex.io”,
/
* The name of your app. /
“appName”: “identity-test”,
/
* Your client id. /
“clientId”: “identity-test:default”,
/
* Your client secret. /
“clientSecret”: “ByGPQeWYm77ltuAqFylvdM/ZQso3oWzgJQWle1r3Xzk=”,
/
* Comma separated list of cultures.
*/
“cultures”: “en”,
"hosts": {
"__localhost": {
/*
* The url to your squidex server.
*/
"url": "https://cloud.squidex.io",
/*
* The name of your app.
*/
"appName": "identity-test",
/*
* Your client id.
*/
"clientId": "identity-test:default",
/*
* Your client secret.
*/
"clientSecret": "ByGPQeWYm77ltuAqFylvdM/ZQso3oWzgJQWle1r3Xzk="
}
What have you tried? Ignore the “hosts” setting and focus on the first 4 settings. It should point to your hostname and use the client id and secret from your app.
This is the removed code to create the app. I will have a look if I can export it somehow from an old sample. But I really do not want to give general support for identity anymore.
