ok, I will try and update the result here.
This seems like a drawback for us. Is there any plan to make this configurable through the UI?
Hi @maliming, does it mean there is no UI to configure it and we need to manage the claims in code?
we are using "client_credentials" & "authorization_code" grant types.
Hi @maliming, I have checked the OpenIddictDataSeedContributor, but there are some features that available in IdentityServer but missing in OpenIdDict.
With IdentityServer, we can create the Api Resources and Identity Resource using the following screens:
<br>
And then we can configure the Api Resource & Identity Resources for a Client:
How can we achieve these features with OpenIdDict?
Hi @liangshiwei, noted, thank you!
Hi @liangshiwei, Thanks for your prompt reply.
I saw this statement in the migration guide: https://docs.abp.io/en/abp/latest/Migration-Guides/OpenIddict-Step-by-Step:
"The Identity Server team has decided to move to Duende IDS and ABP will not be migrated to the commercial Duende IDS. "
If ABP does not migrate to the commercial Duende IDS, how can you support it if we encounter any issues? Additionally, will the next release of ABP be compatible with the commercial Duende IDS?
Hi @maliming, yes, I know that IDS support has been ended in 2022, just want to know if ABP continues to ship IDS-related packages in ABP 8?
Hi @maliming,
Noted. Thanks for the support.
Hi @maliming,
I have sent you the api-definition file via email as requested.
Thanks
Hi @maliming,
I have upgraded to the latest version and got this error:
Hi @maliming, following your steps, I managed to add the custom claim into id token.
Thanks a lot for your help.
