[JBoss JIRA] Commented: (JBAS-2352) Enhance FORM based authentication to allow for transparent auth, error messages
by David Fuelling (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-2352?page=com.atlassian.jira.plug... ]
David Fuelling commented on JBAS-2352:
--------------------------------------
I'd like this functionality as well -- is there no other way to add a "remember me" cookie when using form-based auth? (I'm using JBAS 4.2.3GA).
> Enhance FORM based authentication to allow for transparent auth, error messages
> -------------------------------------------------------------------------------
>
> Key: JBAS-2352
> URL: https://jira.jboss.org/jira/browse/JBAS-2352
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Web (Tomcat) service
> Affects Versions: JBossAS-4.0.3 Final
> Environment: All
> Reporter: Chris Lee
> Attachments: auth.zip
>
>
> Presently FORM based authentication does not allow developers to provide common functionality such as 'remember me' cookies, transparent authentication (from request attributes), and login failure error messages (somewhat addressed by ExtendedFormAuthenticator)
> These can be accomplished by extending the existing functionality (FormAuthenticator); unfortunately, the FormAuthenticator that ships w/ JBoss 4.0.3 does not have the necessary hooks for this.
> The attached code (auth.zip) demonstrates how we accomplished this; the primary change is in BaseCustomFormAuthenticator, with the addition of:
> 1) getUserCredentials method that looks for user credentials in the request (remember me cookie, IP address, query string, etc.)
> 2) getCredentialsFromFormFields that pulls credentials from j_username and j_password - can be extended to pull other attributes as well
> 3) Addition of onFailedAuthentication hook to allow for inserting authentication exceptions into request scope
> 4) Addition of inlineAuthentication flag (set if credentials are found in request) to prevent restoring original request (in the case of inline auth, this is the original request)
> The default implementation matches existing behaviour; see ChoicesFormAuthenticator for an example of how behaviour can be extended.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months
[JBoss JIRA] Created: (EJBTHREE-1769) Remove installation of TimerService from Plugin
by Andrew Lee Rubinger (JIRA)
Remove installation of TimerService from Plugin
-----------------------------------------------
Key: EJBTHREE-1769
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1769
Project: EJB 3.0
Issue Type: Task
Components: plugin
Reporter: Andrew Lee Rubinger
Assignee: Carlo de Wolf
Fix For: 1.1.3
On Plugin atop Branch_5_x boot:
21:06:47,002 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/home/alrubinger/business/jboss/wc/jbossas/branches/Branch_5_x/build/output/jboss-5.1.0.CR1/server/all/deploy/jboss-ejb3-timerservice-as5.jar/ state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error deploying: JBossTimerServiceFactory
...
Caused by: java.lang.IllegalStateException: JBossTimerServiceFactory is already installed.
...this causes regression in the EJB3 Integration TestSuite "ejbthree1624":
Caused by: java.lang.RuntimeException: Could not lookup object at name "testMcBean" due to an error with the underlying ControllerContext
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months
[JBoss JIRA] Created: (JBAOP-710) The javac - aopc cycle sometimes fails
by Jesper Thuun-Petersen (JIRA)
The javac - aopc cycle sometimes fails
--------------------------------------
Key: JBAOP-710
URL: https://jira.jboss.org/jira/browse/JBAOP-710
Project: JBoss AOP
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Aspect Library
Affects Versions: 2.0.0.GA
Environment: xp, java 1.5
Reporter: Jesper Thuun-Petersen
Priority: Minor
My antscript first calls javac and then aopc.
When java src-files touched by the aopc are edited, the next call to compile will cause javac to fail with the following error:
Compiling 1 source file to U:\projects\Cambio\branches\release_fya_05\projects\medicinkort\client\build
U:\projects\Cambio\branches\release_fya_05\projects\medicinkort\client\src\java\dk\wmdata\pem2\client\gui\medicinkort\MedicinKortControllerImpl.java:28: dk.wmdata.pem2.client.gui.medicinkort.MedicinKortControllerImpl is not abstract and does not override abstract method _setInstanceAdvisor(org.jboss.aop.InstanceAdvisor) in org.jboss.aop.InstanceAdvised
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months