I am trying to setup Forge rock(OpenAM13.0) with OpenDJ 3.0,
deployed Open Am in tomcat and Installed opendj successfully. setup where I end up with an error .
Environment:
- OpenAM(V 13.0).war with Tomcat (8.5.27)
- OpenDJ 3.0.0 for External Identity perupose.
-AS part of the process deployed the OpenAM war and on tomcat and could
able to login in with amadmin.
-Created policy set and policy and reqeust patterns as well.(followed
the forgerock getting started guide:https://backstage.forgerock.com/docs/openam/13/getting-started/).
-Here I installed apache 2.4 webserver could able to see the home page.
Error: when i try to configure the WEb agent I endup with below
error,could not able to proceed further.
But I could able to login from the openam login screen but end up with some session invalid exception in session.log and no session in access.csv log file.I could not able to understand and go further.help on this regard is greatly appreciated.
Attached the screen shot of different logs i got .
[WEbagent_insall_Log][1] - Log during web agent installation
[Session-Log][2] - Log at the server openam side
[OpenaM_access.csv_log][3] log for open am side about the access
[WEbagent Installation][1] screen when I try to install webagent
[1]: https://i.stack.imgur.com/HmCFZ.jpg
[2]: https://i.stack.imgur.com/KX1Tb.jpg
[3]: https://i.stack.imgur.com/jQYUX.jpg
Please help on this.
Thanks
Venkat
Related
I'm trying to use CallbackOnOffline OpenFire plugin to send calls for offline users.
But my web server where I need to receive calls didn't receive it (checked on log)
This is a debug log of plugin:
2018.03.08 17:38:28 com.fotsum.CallbackOnOffline - intercepted message from cm2#jabber2.XX.kz to cm1#jabber2.XX.kz, recipient is available
false
2018.03.08 17:38:28 com.fotsum.CallbackOnOffline - sending request to url='JerseyWebTarget { http://web.XX.kz }'
If I touch this web from the OpenFire server by lynx it's working and I see the call on web server log.
openfire version 4.2.2
CallbackOnOffline version 1.2
OS Debian 8 with Java JRE version 8
Thank you!
I have encountered the same problem almost at the same time of this post.
Do you see the debug log after sending request to? If you see
com.fotsum.CallbackOnOffline - can't get response status
url='JerseyWebTarget { https://xxx.xxx.xx/xxxx }'
java.util.concurrent.ExecutionException:
org.glassfish.jersey.message.internal.MessageBodyProviderNotFoundException:
MessageBodyWriter not found for media type=application/json,
type=class com.fotsum.MessageData, genericType=class
com.fotsum.MessageData.
just like me, maybe I could help.
I resolve this by use maven to build CallbackOnOffline plugin manually.
# git clone https://github.com/igniterealtime/Openfire.git
# cd Openfire/src/plugins/callbackOnOffline
# mvn package
Then the callbackOnOffline.jar located at ./target directory. Upload to your openfire server by admin console and it will work.
SQ 5.6, LDAP plugin 2.0.
I've successfully installed the LDAP plugin and restarted the SQ server. In the log (/opt/sonar/logs/sonar.log) the plugin is apparently deployed, but seemingly no attempt is made to initialize/enable it or connect to the LDAP server.
INFO web[o.s.s.p.ServerPluginRepository] Deploy plugin LDAP / 2.0 / 2910f3981167a70a201ccfae01471dfd26c794b7
.
.
INFO web[o.s.s.p.RailsAppsDeployer] Deploying app: ldap
These are the only mentions of ldap/LDAP in the log.
Relevant part of the conf/sonar.properties file:
sonar.security.realm=LDAP
ldap.url=ldap://myldap:389
ldap.user.baseDn=ou=mycompany,ou=People,dc=myurl,dc=com
I believe I've verified ldap.url and ldap.user.baseDn via JXplorer (an LDAP browser).
What really puzzles me is that I don't see anything like the following in the logs, which is what I'd expect from the SQ docs:
INFO org.sonar.INFO Security realm: LDAP ...
INFO o.s.p.l.LdapContextFactory Test LDAP connection: OK
No errors of any kind are noted in the log.
Any idea why SQ is not even apparently trying to kick off LDAP authentication on a restart?
I had the same problem. I'm running Sonarqube using docker. It did not pick up on changes when I restart the server from the Sonarqube UI. Only after restarting the docker image it could pick up the changed file.
Well, now it just started working. I don't have an answer as to why though. Maybe something changed with my LDAP server, or there was some latency that needed to be overcome. I didn't change anything on my end that I'm aware of. In any case, thanks to those that responded.
After countless hours of trial end error I finally figured out how to get cassandra 1.2 and usergrid 1.x up and running and talking to each other. "cassandraAvailable" : true, the keyspace has been created (by calling /system/database/setup and /system/superuser/setup). Then I installed Portal end see the login screen, but neither my sysadmin nor my test account, which I configured in usergrid-default.properties are accepted. Also I can not register a new user. It says "Error registering:" and nothing else.
Where can I look for error logging? What do I have to set to get Usergrid Portal working?
Thanks for your help!
First, make sure you are using the correct URL to log into the portal, you will need to repeat the host twice so the portal knows what Usergrid instance you want to interact with.
http://[host]:8080/usergrid-portal/?api_url=http://[host]:8080
If you are running on Tomcat (make sure you are using Tomcat 7 for Usergrid 1.x) then you can look at the Tomcat logs for Usergrid issues.
I'm using openAM 10.0.0 and the admin guide mention it support conditional login (just no on console):
com.forgerock.agents.conditional.login.url
Then I configure agent as local config:
com.forgerock.agents.conditional.login.url[0]= songjing.com|http://openam.songjing.com:8080/openam/UI/Login
om.forgerock.agents.conditional.login.url[1]= brandA.songjing.com|http://openam.songjing.com:8080/openam/UI/LoginBrandA
When I browse to brandA.songjing.com, it still go back to http://openam.songjing.com:8080/openam/UI/Login login page. I thought it is cause by
com.sun.identity.agents.config.login.url[0] = http://openam.songjing.com:8080/openam/UI/Login
And remark it.
Then end up with error say com.sun.identity.agents.config.login.url not found.
I try with web agent 3.0.4 and 3.1 for apahche httpd, both not working
Any help?
Rgds
SJ
Solved. web agent 3.0.4 not support conditional login url.
for web agent 3.1 the key is:
com.forgerock.agents.conditional.login.url
and for j2ee agent 3.1 the key is
com.sun.identity.agents.config.conditional.login.url
and due to I use virtual server, I need configure fqdn mapping:
com.sun.identity.agents.config.fqdn.mapping[branda.com] = branda.com
I am a newbie.I am using Weblogic 10.0.0.0..I am getting an validation error in first page(Login Page wit user name and pwd) as "logger is not initialized",while deploying. I do the same thing with tomcat, and the .war is imported and deployed is success. What is the reason? and also ,in weblogic 10.0.0.0 we have two jdk's(jdk 1.6 and Jrockit)...in my system i m having 1.6.0_17..so which one it takes.i forgot which i choose while installing..whether it takes from wblogic jdk or which one?..wher i m going wrong..its a small one i notice..but could not figure out..plz lemme kno??
This is either because you haven't configured your WLS installation correctly. When you first setup your console there is a parameter you have to change in your auth file that if not set with cause this issue.
Or you are selecting logging during deployment from the admin console and you haven't configured log4j in your application.