Single Sign-On and Network Drive

[HLidstrom]

Exploring User Security and single sign-on does not work when the model file is stored on a network drive. It works when the model is stored on my local drive, however. Does anyone have an idea what may be the problem?

This is what I tried.
1) I created a test model and enabled security. So far so good.
2) I logged in to the model as admin and created a local user. Closed and opened the model. Got a log in prompt and entered the id and password I created in the model. This is what I expected.
3) Now I wanted to try single sign-on. I logged in as admin again, opened the Users dialog and checked off Windows Authentication. Next, I clicked the Import button and found my own id in Active Directory. I imported it, saved and closed the model.
4) I double-clicked the model file. Sparx opened without prompting me for id and password and I could see my Windows Id up in the right corner of the Sparx window. Success! SSO works. (I thought.)
5) Next I copied the EAPX file to a network drive and double-clicked again. Now I got prompted for id and password again. Failure! SSA does not work when the EAPX file resides on a network drive.

I am just an ordinary user, as far as PC and network are concerned. (No admin privilege.) There isn't much troubleshooting I can do. Does anyone have an idea why SSO works when the model resides on a local file, but not when it sits on a network drive? Something I could ask my IT support to look into?

Thanks!

[Geert Bellekens]

Windows authentication is disabled each time you move the .eap(x) file to another drive.
You can go in with the admin user and disable/re-enable again.

But if you are serious enough to enable windows authentication, I don't think you should be playing around with .eap(x) files, which are MS-Access files with another extension.
Go for the professional approach and use a database (MySQL or SQL Server are most popular and seem to work best)

Geert

[Sunshine]

Windows authentication is disabled each time you move the .eap(x) file to another drive.
You can go in with the admin user and disable/re-enable again.

But if you are serious enough to enable windows authentication, I don't think you should be playing around with .eap(x) files, which are MS-Access files with another extension.
Go for the professional approach and use a database (MySQL or SQL Server are most popular and seem to work best)

Geert

Sharing eap(x) or feap files on a network drive can cause problems and waste a lot of time. I concur with that advice from Geert regarding moving to MySQL or SQL.  Also add stay away from Oracle DBs as they suffer from performance issues with Sparx EA unless you have a Oracle DB Guru.

[HLidstrom]

Thanks for the good advice. We are a small team in a large organization. It will take us a while to go through all the hurdles for a server based solution and we need to get started with our model. We will have to live with a shared eapx for a while.
(Maybe with replication as well, to work around slow performance on the shared drive. Which will just add another layer of complexity.)

We do what we have to do.
/Håkan

[Geert Bellekens]

Thanks for the good advice. We are a small team in a large organization. It will take us a while to go through all the hurdles for a server based solution and we need to get started with our model. We will have to live with a shared eapx for a while.
(Maybe with replication as well, to work around slow performance on the shared drive. Which will just add another layer of complexity.)

We do what we have to do.
/Håkan

Whatever you do, don't use replication. If that gets corrupted (and it does) you really end up in a pickle.

Geert