-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 7.0.0 DXP FP27, Master
-
Fix Version/s: 7.0.0 DXP FP31, 7.0.5 CE GA6, 7.0.X, 7.1.X, Master
-
Component/s: Application Security > Open SSO
-
Branch Version/s:7.0.x
-
Backported to Branch:Committed
-
Story Points:1
-
Fix Priority:4
-
Git Pull Request:
a) Start with a Liferay 7 tomcat bundle, unpack it.
b) Deploy the osgi configuration file for the OpenSSO connector, to osgi/configs. <----- CRITICAL
....Filename should be:
........com.liferay.portal.security.sso.opensso.configuration.OpenSSOConfiguration.config (copy is attached)
d) Prepare a blank DB, ready to receive the Liferay schema.
e) Configure portal-ext.properties to connect to the DB.
f) Startup Liferay
g) Wait until Liferay finishes running all SQL scripts to create the schema, then connect to the DB using an SQL admin utility, and check the contents of portletpreferences using the following SQL query:
select preferences from portletpreferences where portletid = 'com.liferay.portal.security.sso.opensso'
The actual result it creates <portlet-preferences>...a bucket load of config here...</portlet-preferences> of which it's unwanted.
But if you deploy the OpenSSOConfiguration.config file to the osgi/configs after the DB has initialized, then you are able to see the expected result of preferences = <portlet-preferences /> from the table