Book a Demo

Author Topic: Sparx EA Cloud deployment - AD domain placement  (Read 4484 times)

shas

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Sparx EA Cloud deployment - AD domain placement
« on: April 15, 2016, 02:32:28 pm »
Hello SMEs,
I would like to enable windows AD authentication for Sparx EA which uses DBMS repository. Do I need to have the EA client (user machine) and database connected to the AD domain? In case if I use Sparx Cloud Service as well, does that need to be part of the AD domain? The question comes up because I am intending to install the system on Azure Cloud. Hence trying to understand which components need to be part of the AD domain and which can be part of public cloud.

Appreciate any guidance on the above.

Shas

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Sparx EA Cloud deployment - AD domain placement
« Reply #1 on: April 18, 2016, 09:05:08 am »
Neither the cloud service or DB server need to be part of the AD domain.

The user importing Active Directory is the only part that really needs to be part of the domain. The users logging in are just matched against the domain username.

One point to be aware of when using the cloud with AD, EA imports the usernames but not a password from the domain. The http authentication of the cloud server will need an explicit password set to be able to authenticate anyone. The exception to this is that if IIS is used, it can be configured to look up the entered credentials against a domain. (In which case it will need to be part of the domain)