The example fails to run

[qq1176914912]

Hello, excuse me, I configured the client according to Delegation or Impersonation , but when I ran your corresponding sample, there was an error in changing the position in "ShopApi" :

[qq1176914912]

There is also this demo:wsfederation, I found that you must use the "administrator" account to log in, if you use another account to log in, 5001 will appear this error:

[simpleidserver]

Both issues are fixed in the master branch.

[qq1176914912]

Both issues are fixed in the master branch.

Both issues are fixed in the master branch.

Thank you for your modification. For wsfederation, I tested it and found that when 5001 was deployed locally (localhost), I could successfully log in using other accounts. However, when I deployed 5001 to a remote server (accessed through the domain name), I logged in using the account "administrator" normally. But when I use other accounts, the demo will report an error, what is the situation?

[simpleidserver]

Could you make the modifications in your client to show the "PII" and copy the error into the conversation?

For more information, please refer to the official documentation:

https://learn.microsoft.com/en-us/dotnet/api/microsoft.identitymodel.logging.identitymodeleventsource.showpii?view=msal-web-dotnet-latest

[qq1176914912]

Could you make the modifications in your client to show the "PII" and copy the error into the conversation?

For more information, please refer to the official documentation:

https://learn.microsoft.com/en-us/dotnet/api/microsoft.identitymodel.logging.identitymodeleventsource.showpii?view=msal-web-dotnet-latest

Ok, this is I in the project with "IdentityModelEventSource. ShowPII = true;" The result of

[qq1176914912]

Is it because I arbitrarily changed the encryption of the user password? I changed the way you previously stored your password (to the database).I'm using postgresql

[qq1176914912]

Could you make the modifications in your client to show the "PII" and copy the error into the conversation? For more information, please refer to the official documentation: https://learn.microsoft.com/en-us/dotnet/api/microsoft.identitymodel.logging.identitymodeleventsource.showpii?view=msal-web-dotnet-latest

Ok, this is I in the project with "IdentityModelEventSource. ShowPII = true;" The result of

Hello, excuse me. I see your modified version number: "031333" f6fc1d9d1b5bfb43e2a30c86abcbb776df, before I use my old "postgresql" test, when we use the other account can normal login, but the sqlite library for the old version is wrong before, There is no problem if I ask the program to create a new "sqlite" library, so what do I do with the old version of the sqlite library? Do you want to clear a table?

[qq1176914912]

Could you make the modifications in your client to show the "PII" and copy the error into the conversation? For more information, please refer to the official documentation: https://learn.microsoft.com/en-us/dotnet/api/microsoft.identitymodel.logging.identitymodeleventsource.showpii?view=msal-web-dotnet-latest

Ok, this is I in the project with "IdentityModelEventSource. ShowPII = true;" The result of

Hello, excuse me. I see your modified version number: "031333" f6fc1d9d1b5bfb43e2a30c86abcbb776df, before I use my old "postgresql" test, when we use the other account can normal login, but the sqlite library for the old version is wrong before, There is no problem if I ask the program to create a new "sqlite" library, so what do I do with the old version of the sqlite library? Do you want to clear a table?

Excuse me, do you have any ideas? I don't want to recreate the library.

[qq1176914912]

With your latest master project, there was a problem testing FapiGrantManagement:

[simpleidserver]

Hello,

Regarding the WS-Federation issue:

Can you clean the "SerializedFileKeys" table and try again?

For FAPI Grant-Management:

The issue is fixed in the master branch.

[qq1176914912]

Hello,

Regarding the WS-Federation issue:

Can you clean the "SerializedFileKeys" table and try again?

For FAPI Grant-Management:

The issue is fixed in the master branch.

Regarding the WS-Federation issue: Thank you for your suggestion that the "SerializedFileKeys" table cannot be cleared. If clearing the table would cause the 5001 program to fail to start, I found that simply deleting the account with this error and adding it again could solve the problem.

And I also found a new problem, using the latest mater project, when using sqlite, when the application automatically creates sqlite libraries, there is an error message:

For FAPI Grant-Management: Thank you. Problem solved

[simpleidserver]

An exception was thrown during startup because the migration scripts were not applied before the AutomaticConfigurationProvider class tried to get values from the table. A check has been added in the "KeyValueRepository" and the issue is now fixed.