Overview
SAMO Browser was developed as a substitution for old LIDS Browser and is available since the Dynamic App v. 8.14.0.
Installation
SAMO Browser is a Dynamic-app component and will be installed together with it. However, some additional Gateway configuration regarding proxies is needed.
Prerequisites
- LIDS Application Server > 8.13.2
- SAMO Gateway > 10.X.
- SAMO User Service > 10.X.
don't forget to set the correct server properties for SAMO Gateway and for SAMO User Service if those components are not yet running on your SAMO LIDS project!
Gateway configuration
applications
To get an individual application running on SAMO Gateway for SAMO LIDS Browser, you also need to define the appropriate application in Gateway metadata. Please refer to the actual configuration according your needs and the possibilities of the actual SAMO Gateway
{
"mode": {
"type": "session",
"sessionExpiration": 3600000
},
"defaultDataSource": "jndi:jdbc/ASSECODS",
"defaultAuthorization": {
"type": "roles",
"requiredRole": "APPLICATION:SAMO_LIDS_BROWSER.APPRUN"
},
"clients": [
"samo-lids-browser-client"
],
"proxies": [
"lids",
"user-service"
],
"authenticationMethods": [
{
"type": "basic"
},
{
"type": "rememberMe",
"configurationProperty": "gateway.rememberMe"
}
],
"userDetails": {
"type": "security"
},
"credentialsVerification": [
{
"type": "security"
}
],
"accountStatusCheck": [
{
"type": "security"
}
]
}
The defined role in the example, with its method (APPLICATION:SAMO_LIDS_BROWSER.APPRUN) has to be created manually in SEC_APPLICATION and SEC_MEHTOD tables. The specified dataSource has to be configured correctly in the used application server.
clients
In the example, the Dynamic App version is set in clients.xml. It's also possible to use some variable from project.properties. In KB the available SAMO Dynamic App can be seen for the individual versions.
{
"configurationPathProperty": "dynamicApp.configurationLocation",
"configurationParts": [
"samo-lids-browser"
],
"components": {
"dependencies": {
"@samo/dynamic-app": "8.22.3"
}
}
}
proxies
Since the new SAMO Browser works with new Rest API endpoint, it must be included in the proxy configuration in file gateway\proxies\lids.json. This step does not have to be followed, if you are using samo-base package > 11.3.0.
"/api**": {
"proxyUrl": "${lids.url}/api/rest"
}