Anyway I can custom Jboss EAP 7 management console login page by adding Log-on Warning Banner in it?
HAL is protected by digest authentication. And as such the browser takes care of the login. Bottom line you won't be able to customize the login.
HAL is the project behind the web console in WildFly: https://hal.github.io/
You can customize it there with extensions (i don't really know the details)
Related
I am working on wicket version 1.4.17 in my application with tomcat 7.
After updating tomcat my application is broken.
The login page is not working when submit is clicked. It is working when I hit enter in the url.
If I click on the login button it is returning the same page, but if I login again then it is working.
Your problem might be related to Tomcat changing the session id after login.
Hard to tell whether your code or Wicket can't handle it, but 1.4.x is discontinued already.
I have two WARs in an EAR. Each WAR has its own login.jsp and logout.jsp.
Logging in via webapp1 works fine, and then when I browse to webapp2, I'm also logged in there. If I go to webapp1/logout.jsp, I get logged out of both applications (browsing to webapp1 or webapp2 both give me a login page).
However, if I log in via webapp1, but try to log out using webapp2/logout.jsp, it has no effect. If I navigate to webapp1/index.jsp or webapp2/index.jsp, I'm still logged in (and the other way around has the same issue, i.e. log in via webapp2 but logout via webapp1).
The logout.jsp calls:
session.invalidate();
request.logout();
I'm using Jboss EAP 6.1.
Any suggestions?
Thanks.
Turns out we'd added the <sso /> element to the <virtual-server... element in standalone.xml, but we'd also added the SingleSignOn valve to the jboss-web.xml of each WAR. It appears that the latter was adding a second singlesignon valve in to the chain.
So, removing the valves from the jboss-web.xml files fixed the issue - the <sso /> tag is sufficient to enable sso (despite what a lot of blog posts on the internet claim).
(I don't feel too bad finding out it was my mistake given that no one else answered my question.)
I am trying to do authentication in spring mvc application using picketlink with jboss 7.
I have configured web.xml,jboss-web.xml,standalone.xml for custom login module,
picketlink-idfed.xml,picketlink-handlers.xml.
I have my customlogin module which extends Databaseserverloginmodule.
When I try to login I am getting blank page as 404 error and my customlogin module is not called as authentication is not happening.
Am i missing any configuration?
Any help would be appreciated
New to JAVA. I developed Web application(JSP) successfully delpoyed on TOMCAT 6.0. Now the client want to use external SSO to authenticate users. As of now when the users are authenticated the website is displayed with Login Page where the user has to login again.
I am using the Login.jsp to bring the user roles from the SQLDB for Website.
What I want to accomplish now is when User is authenticated login.jsp should retrieve the credentials from the SSO and display the website thus accomplishing the purpose of Single sign on process.
I read a lot from this forum and other websites but kinda lost in the process.
Any help would be appreciated.
thank you
We developed a Tomcat extension (valve) which does just that. Basically you use standard J2EE security (role-ref etc) in your app and our Tomcat valve then acts as a bridge between Tomcat and our SSO platform. You can find out more at www.cloudseal.com
Of course you may not want to use our SSO platform :-( but you can still use our Tomcat valve and modify it to fit your needs. It's released under an Apache 2 license and you can grab the source from Github
I have trouble reaching the Administration console of the OpenAM server for a second time after a restart of the JBoss applicationserver on Windows 2008 Server R2 Datacenter.
I deploy OpenAM 9.5.2 (the opensso.war file) in the JBoss-4.2.3GA 'deploy' folder of its default profile.
I point my Internet Explorer 8 browser to: my.test.domain.com:8080/opensso
The page appears to create a Default or Custom Configuration for the OpenAM server
I successfully complete the wizard for creating a Custom Configuration
A pop-up with a 'Proceed to login' link appears after completing the configuration
I click this link and I can access the Admin console
Here is the thing:
When I restart JBoss and try to browse to the Admin console URL manually for a second time:
http://my.test.domain.com:8080/opensso/console
It will instead go to the page again to create a Default or Custom Configuration:
http://my.test.domain.com:8080/opensso/config/options.htm
And therefore I cannot access the Admin console anymore.
Note:
I verified that the URL: my.test.domain.com:8080/opensso/console is correct by opening
a second tab in IE8 before the restart of JBoss.
Been looking at doing this myself - this may provide the solution
https://wikis.forgerock.org/confluence/display/openam/Considerations+when+deploying+on+JBoss+AS+5.1
Indeed that will work. I discovered that you can alternatively add in your run.bat of JBoss:
-Dcom.sun.identity.configuration.directory= your configuration directory