Unexpected error when login using M-Files login Services

Hi All,


we are try to use M-Files login Services and setup the federated authentication, joining our m-files server to M-Files Manage and setup the Entra ID permission. But we still encountered the Unexpected Error when redirected to m-files.login.com. we found the URL that are still cannot be accessed on our server. here's the URL. mycompany.domain.com/.../read

{
"scopes": [
{
"tmpScopeName": "*:Windows",
"configurations": [
{
"name": "MFLoginService.Default",
"tmpProtocol": "oauth",
"assembly": "MFiles.AuthenticationProviders.OAuth",
"oauthSettings": {
"server": {
"AccountClaim": "accountname",
"AuthConfClaim": "authconf",
"SubscriptionClaim": "subscriptionid",
"Audience": "mfiles://mycompany.domain.id",
"IdentityProviderMetadata": "https://login.m-files.com/.well-known/openid-configuration",
"ForceDownLevelAccountName": "false",
"AccessTokenType": "JWT",
"PreserveClientSpecificSetting_Scope": "true"
},
"client": {
"Protocol": "OAuth 2.0",
"RedirectUri": "http://localhost/signin-oidc",
"ClientID": "mfclient, 39adf7a2-fd79-4a16-9581-42ecc710d70a",
"RedirectUriForWeb": "https://mycompany.domain.id/authentication/MFLoginService.Default/read",
"Scope": "openid mfiles://mycompany.domain.id offline_access",
"UseIdTokenAsAccessToken": "false",
"UseAccessTokenInWeb": "true"
}
}
}
],
"defaultConfiguration": "MFLoginService.Default"
}
]
}

and this is our federated authentication configuration. is there any advice to solved the unexpected error ?

Parents
  • There appears to be an extra space in the ClientID field after the comma, so you could try removing it. OAuth can be quite strict in these cases, as some values are treated as exact strings and whitespace is not automatically trimmed.

    If that doesn't help, you can enable logging in the configuration and see if you get any additional details in the Windows logs.

Reply
  • There appears to be an extra space in the ClientID field after the comma, so you could try removing it. OAuth can be quite strict in these cases, as some values are treated as exact strings and whitespace is not automatically trimmed.

    If that doesn't help, you can enable logging in the configuration and see if you get any additional details in the Windows logs.

Children