Book a Demo

Author Topic: How to switch user using v17.2.1721  (Read 2104 times)

ppeeters

  • EA User
  • **
  • Posts: 24
  • Karma: +0/-0
    • View Profile
How to switch user using v17.2.1721
« on: August 07, 2026, 11:54:59 pm »
Hello,

Since the ability to switch user has been removed from 17.2.1721 ('Login as another user' ), how can I switch to an administrative user if the cloud repository is configured for Windows and OpenID authentication ?
On window, it automatically authenticates using the windows user and then I'm stuck.

PeterHeintz

  • EA Practitioner
  • ***
  • Posts: 1004
  • Karma: +59/-18
    • View Profile
Re: How to switch user using v17.2.1721
« Reply #1 on: August 13, 2026, 07:24:33 pm »
Good question!
I ask myself how an admin can work without admin rights!?!
Best regards,

Peter Heintz

Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1186
  • Karma: +30/-8
    • View Profile
Re: How to switch user using v17.2.1721
« Reply #2 on: August 18, 2026, 06:15:30 pm »
Hello,

Since the ability to switch user has been removed from 17.2.1721 ('Login as another user' ), how can I switch to an administrative user if the cloud repository is configured for Windows and OpenID authentication ?
On window, it automatically authenticates using the windows user and then I'm stuck.
Hello Peter, have you tried running Sparx EA as a different user. To run as different user shift and right click on the application. How to achieve this differs depending on the version of Windows you are running and the policies applied to your laptop.

You could also try running the following command from a command line or PowerShell:
Code: [Select]
runas /user:DOMAIN\UserName "C:\Path\App.exe"

PeterHeintz

  • EA Practitioner
  • ***
  • Posts: 1004
  • Karma: +59/-18
    • View Profile
Re: How to switch user using v17.2.1721
« Reply #3 on: August 19, 2026, 05:31:38 pm »
Hi,
no I have not tried this but it will also not work for us currently.
We have for each for each user a local admin account with password (nor know by our ADS). Funnily in the user manual of V17.2 this still reommended to have but how to login is now unclear. I will try if a EA shortcut file can be used if I have time to.
However I do not understand why this feature is removed.
Best regards,

Peter Heintz

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13531
  • Karma: +576/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: How to switch user using v17.2.1721
« Reply #4 on: August 19, 2026, 11:56:18 pm »
However I do not understand why this feature is removed.

I'm guessing it's removed because of the big security vulnerabilities scare.
Apparently, after Sparx dismissed the direct reports, the vulnerabilities where publically published.
This apparently lead to a bit of a panic at Sparx to quickly fix all security related issues.
See also the disablement of Repository.Execute(), and the new restrictions on Repository.SQLQuery (none of which was announced in the release notes)

Geert

ppeeters

  • EA User
  • **
  • Posts: 24
  • Karma: +0/-0
    • View Profile
Re: How to switch user using v17.2.1721
« Reply #5 on: August 21, 2026, 05:02:08 pm »
You could also try running the following command from a command line or PowerShell:
Code: [Select]
runas /user:DOMAIN\UserName "C:\Path\App.exe"
Enterprise policies generally prohibit from having multiple accounts on the same corporate device. It just so happens that I have such an local admin account so I can test this.
It is indeed possible to be authenticated using that principal and then assigned the user to an Administrator group. By the way, the last action is only possible if you still can authenticate as an admin. I could do that using Sparx EA 17.0 which still allow to switch user.
The majority of our users do not have such a dual AD account hence cannot use that trick.

Another possibility is to disable Windows authentication for the repository while keeping OpenID. The OpenID authentication workflow still gives the opportunity to cancel it and to fall back using the user/pass authentication method.

Those workaround look like kludges. In the end, it boils down to the ability to support user roles at the repository level. Once authenticated, you should be able to select the role you want to use for a given work session.