Integrating M-Files with Okta Skip to main content
https://support.okta.com/help/answers?id=9062a000000xznjqaw&refurl=http%3a%2f%2fsupport.okta.com%2fhelp%2fanswers
How satisfied are you with the Okta Help Center?
Thank you for your feedback!
How satisfied are you with the Okta Help Center?
1
2
3
4
5
Very Dissatisfied
Very satisfied
Enter content less than 200 characters.
Ask Search:
Jason FareJason Fare 

Integrating M-Files with Okta

Just wanted to post some configuration help for anyone trying to integrate M-Files with Okta.

After 6 weeks working with M-Files, we finally figured out what was required.  This could be converted into a template if I knew how.

Single Sign On URL:
https://<CustomerName>.cloudvault.m-files.com/Authentication/MFiles.AuthenticationProviders.Core/read

Recipient URL:
https://<CustomerName>.cloudvault.m-files.com/Authentication/MFiles.AuthenticationProviders.Core/read

Destination URL:
https://<CustomerName>.cloudvault.m-files.com/Authentication/MFiles.AuthenticationProviders.Core/read

Audience Restriction:
https://<CustomerName>.cloudvault.m-files.com

The rest was all the defaults except that you have to provide an assertion. They may use the WS-Federation terminology when talking to you and call it a claim.  But I had to create an Attribute Statement:
Name: AccountClaim
Name Format: Unspecified
Value: user.email

Wanted to make sure anyone else going through this doesn't have as much of a struggle as I did.  You will also have to tell M-Files that the name of the "Claim" is AccountClaim so M-Files can update a registry item on their side. 

Once you get it all working, make sure you remind M-Files to "persist" the change or you'll have to go through it again when M-Files reboots/patches their servers.

HTH!

-Jason


 
Best Answer chosen by Jason Fare
Jason FareJason Fare
This was the part that was needed which was outside of their documentation:

I had to create an Attribute Statement:
Name: AccountClaim
Name Format: Unspecified
Value: user.email