Installing Whydah

| | The Readme.MD file of the Whydah github repos contains detailed installation information and start-up scripts |

Release notes

Whydah Releases

A typical production installation of Whydah:

Unknown macro: {gliffy}

Using DNS & mod_balance load-balancing

Load-balancing

Amazon's Elastic Load Balancing (We use this for AWS deployments)
Round-robin_DNS and Apache mod_balance (We use this for on-premise deployments)
Apache only load-balancer: How To Set Up A Loadbalanced High-Availability Apache Cluster

Installation guides

See Whydah infrastructure recommendations for particular tips on infrastructure setup.

Linux

[Install SSOLoginWebApp on Ubuntu]
[Install SecurityTokenService on Ubuntu]
Install UserIdentityBackend
[Install UserAdminWebApp on Ubuntu]
[Install apache web proxy on Ubuntu]

Integration setups

Integrating with Whydah

See TestWebApp for an example on how to integrate your application with Whydah. The github repository includes examples in Java, JavaScript,
Django, Microsoft Sharepoint App and Spring Security.

Default ports for the whydah services

Whydah Module	Default Port
UserIdentityBackend	9995
SecurityTokenService	9998
UserAdminService	9992
UserAdminWebapp	9996
SSOLoginWebApp	9997
CRMService	12121
SPAProxyService	9898
OAUTH2Service	8086

IAM_MODE

IAM_MODE is used to run the modules in different mode

IAM_CONFIG

IAM_CONFIG is used to define your own config-file for Whydah. File-names are relative to current directory. Example:

Unknown macro: {code}

java -jar -DIAM_CONFIG=useridentitybackend.TEST.properties UserIdentityBackend.jar