This content has been marked as final.
Show 5 replies
-
1. Re: Different login successful message.
asiandub May 30, 2011 3:34 PM (in response to tdtappe)Using Seam-Config to configure SecurityEventMessages should be a good way...
I'd try to use @Alternative in conjunction with overwriting SecurityEventMessages
enabled = true
to
enabled = false
-
2. Re: Different login successful message.
tdtappe Jun 1, 2011 4:18 AM (in response to tdtappe)Thanks Jan. I've got it working now :-)
The most important hint was the
enabled
property. I only had a look at CR2 - and there wasn't such a property at that time.Disabling SecurityEventMessages via seam-config and using my own observer on PostAuthenticate did the trick.
--Heiko
-
3. Re: Different login successful message.
asiandub Jun 1, 2011 4:21 AM (in response to tdtappe)
I only had a look at CR2 - and there wasn't such a property at that time.Yep, Seam 3 is still rather a
fluent API
, at least in some places ;-) -
4. Re: Different login successful message.
mdzhokanov Sep 14, 2011 5:12 PM (in response to tdtappe)Heiko, could you share your beans.xml? I modified mine according to the Seam-Config documentation, but the Login Successful message keeps coming up. Here is my beans.xml:
<?xml version="1.0"?>
<beans xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:s="urn:java:ee"
xmlns:security="urn:java:org.jboss.seam.security"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://jboss.org/schema/cdi/beans_1_0.xsd">
<!-- this works correctly -->
<security:IdentityImpl>
<s:modifies />
<security:authenticatorName>UsersAuthenticator
</security:authenticatorName>
</security:IdentityImpl>
<!-- event messages keep coming up -->
<security:SecurityEventMessages>
<s:modifies />
<security:enabled>false</security:enabled>
</security:SecurityEventMessages>
</beans> -
5. Re: Different login successful message.
ssachtleben.ssachtleben.gmail.com Sep 14, 2011 5:42 PM (in response to tdtappe)Not sure about the beans.xml configuration, but you could inject SecurityEventMessages and set enabled false.
The messages will be disabled by default with the upcoming 3.1.0 release.