-
Notifications
You must be signed in to change notification settings - Fork 7
Upgrade process from 4.1 to 4.2
-
Move /etc/gluu/conf/casa.json contents to database (as in https://github.com/GluuFederation/casa/issues/96)
-
If /opt/gluu/jetty/casa/casa-cors-domains exists, create a new key in the json configuration whose value is an array of strings. Every element of the array must contain every line found in the file
Example:
If casa-cors-domains
contains
http://acme.com
https://some.gluu.foo
we should add to oxConfApplication
the following:
allowed_cors_domains: ["http://acme.com", "https://some.gluu.foo"]
Examine the *.jar files in /opt/gluu/jetty/casa/plugins
Temporary extract the contents and see META-INF/MANIFES.MF
and collect the values of Plugin-Id
property
Remove the jar files and download the new corresponding versions using the table below:
If strong-authn-settings
is found, additionally do the following:
In oxConfApplication
json content add:
"basic_2fa_settings": {
"autoEnable": false,
"allowSelfEnableDisable": true,
"min_creds": the same value of property min_creds_2FA of casa.json
},
"plugins_settings": {
"strong-authn-settings": {
"policy_2fa" : Copy the value of property policy_2fa found in original casa.json (if any)
"trusted_dev_settings": Copy the value of property trusted_dev_settings found in original casa.json (if any)
"basic_2fa_settings": the same contents used in outer basic_2fa_settings above
}
}
If account-linking
is found, additionally do the following:
-
Copy to /opt/gluu/jetty/oxauth/custom/pages the new casa.xhtml file
-
In the database, update attribute oxScript of the custom script with displayName=casa