On startup of RSA, even with a new workspace the following error pops up:
An internal error occurred during: "Installing Worklight Development Server".
Attempted to endRule: null, does not match most recent begin: R/. See log for trace information if rule tracing is enabled.
Worklight 6.2 supports RSA version 9.0 only. Please make sure that is the version of RSA that you are using. Other versions are currently not supported.
Related
I have a console app that runs with no error on my system with windows 10.
on server with windows server 2016 or 2019 I have Security warning: the negotiated tls 1.0 is an insecure protocol...
as I understood, .net core versions support tls 1.2! so whats wrong?
How can I find out what part of my code cause this problem?
so far I think that this warning occurs when my app wants to connect to DB
Security warning
I am using Rs.exe for automatic deployment of report files. When older versions of SSL and TLS are disabled , and only TLS 1.2 is enabled. Deployments are failing.
I am getting below error:
Could not connect to server: https://ServerName/reportserver/ReportService2010.asmx
Things I tried:
I added following registry entries as per
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/cc1cc0c5-65d0-48ac-a0b4-a689b9e6a2bd/2016-report-builder-connection-difficulty-with-tls-12-only-?forum=sqlreportingservices
Still no luck :(
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001
"SystemDefaultTlsVersions"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001
"SystemDefaultTlsVersions"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions"=dword:00000001
OS - Windows Server 2016
SQL - SQL Server 2016
.NET framework - 4.7.1
Proper certificate is installed in server.
https://ServerName/reportserver is accessible in browser.
All valid configurations are done in RS Configuration Manager
Any help would be appreciated. Thank You!
I have a server which has been upgraded from IBM Worklight 6.0 to IBM Mobilefirst 6.3
The server is currently running older versions of my mobile application, which do not have AppAuthenticity enabled.
When I uploaded the newer version of Application, AppAuthenticity option became enabled ONLY for one (windows) environment, while others stayed disabled.
After a restart, Windows Environment version became like others, while iPAD environment started giving option to change the AppAuthenticity.
I listed the application through WLADM CLI, and it gave me below error:
XML validation error, reading from
https://URL/wladmin/management-apis/1.0/runtimes/worklight/applications/MYAPPS?locale=en_US:
cvc-complex-type.4: Attribute 'downloadLink' must appear on element
'applicationEnvironmentDataAccess'.
Please note, the application if ran alone on other server is working fine with same Application-descriptor and WAR file, only when Old and new versions are uploaded on same server, this problem comes.
Are you saying your server has a single .war file with 2 apps on it, one from 6.0 and one from 6.3?
There are very different Application Authenticity Protection implementations in 6.0 and 6.3. These cannot co-exist in the same single .war file.
You need to deploy to your application server 2 .war files - one for handling the 6.0 app and another for handling the 6.3 app.
Relevant user documentation can be read here: http://www-01.ibm.com/support/knowledgecenter/SSHS8R_6.3.0/com.ibm.worklight.upgrade.doc/devenv/c_upgrade_to_srvr_in_production_env.html
As Idan said, the 6.0 and 6.3 app can not be handled together, since I only wanted to enable the App Authenticity in the newer version, what I did as a workaround was to connect via WLADM tool and disable the App Authenticity for Older Versions via command line.
Below are the commands one needs to use:
\Worklight\shortcuts>wladm --url=https://server.url/wladmin --user=admin --passwordfile=password.properties
to verify the application's current Authenticity :
app version %CONTEXT% %APP_NAME% %Environment_Name% %versionCode% get authenticitycheckrule
To Disable
app version %CONTEXT% %APP_NAME% %Environment_Name% %versionCode% set authenticitycheckrule DISABLED
Anyone know how to configure v6.2 to LDAP to authenticate on the console (localhost:10080/worklightconsole/). On v6.1, this is done in authenticationConfig.xml but the migration process to v6.2, automatically removed all the configuration that was configure to use LDAP to secure the console with this comment:
"IBM migration removed customSecurityTest named WorklightConsole. IBM migration removed realm named WorklightConsole. It is not supported as of Worklight v6.2"
I have already tried following this PDF and still not working - http://public.dhe.ibm.com/software/mobile-solutions/worklight/docs/v620/09_11_Using_LDAP_login_module_to_authenticate_user_with_LDAP_server_in_hybrid_applications.pdf
Thanks
In previous versions of Worklight, Worklight Console protection was handled by Worklight's security framework. Starting v6.2, this is now handled by the underlying application server, be it WAS, WAS Liberty profile or Tomcat.
In Worklight Studio WAS Liberty profile is used, so you will need to follow these instructions: http://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/appcenter/t_ac_lib_ldap.html?lang=en
For other application servers follow the relevant instructions from here: http://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/appcenter/c_ac_ldap_jndi.html?lang=en
I am trying to install and configure Worklight application center on liberty profile.
I have installed the worklight 6.2 using the installation manager. Along the installation process i have installed the appcenter as well.
The installation was successful. But when i try to access the console it giving me "Context root not found".
Also I have checked the server.xml of the liberty server. It contains the appcenterconsole.war and the applicationcenter.war mapped.
Does anyone experience this problem as well?
This might be the same problem as mentioned here: Worklight Development Server does not start
Please make sure you use Oracle Java, not IBM Java!