[JBoss JIRA] Created: (JBMAIL-244) Fetching mail with MalformedHeader from POP3 server
by Ryan Maloney (JIRA)
Fetching mail with MalformedHeader from POP3 server
----------------------------------------------------
Key: JBMAIL-244
URL: http://jira.jboss.com/jira/browse/JBMAIL-244
Project: JBoss Mail
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: JBoss application server 4.0.4-CR2 running on Windows XP Profesional SP2
Reporter: Ryan Maloney
Assigned To: Andrew Oliver
Enabled fetchmail and added a pop3 account. Manually invoked the pop() method via the mx-console and received the following:
[Top part of the stack trace]
INFO [org.jboss.mail.fetchmail.Popper] Found 104 messages (0) new ones
INFO [org.jboss.mail.fetchmail.Popper] Trying to get message 0
INFO [org.jboss.mail.fetchmail.Popper] Message 0 Subject: EMAIL SUBJECT REMOVED
ERROR [org.jboss.mail.fetchmail.Popper]
org.jboss.mail.message.MalformedHeaderException: Malformed Header:
This is a multi-part message in MIME format.
[end snippet]
Mail retrieval ended immediately thereafter.
I have sent the offending header to acoliver(a)jboss.com
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 5 months
[JBoss JIRA] Created: (JBPORTAL-977) 403 error when logging in as admin with LDAP
by Kevin Barfield (JIRA)
403 error when logging in as admin with LDAP
--------------------------------------------
Key: JBPORTAL-977
URL: http://jira.jboss.com/jira/browse/JBPORTAL-977
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Core
Affects Versions: 2.4 Final
Environment: Portal 2.4 CR3 bundled
Reporter: Kevin Barfield
Fix For: 2.4 Final
A 403 error is shown when logging in as admin using LDAP. Open a new browser, and now you are logged in. Same issue with logout. Logging in as a regular user is fine.
Here is the login config:
<policy>
<!-- For the JCR CMS -->
<application-policy name="cms">
<authentication>
<login-module code="org.apache.jackrabbit.core.security.SimpleLoginModule" flag="required"/>
</authentication>
</application-policy>
<application-policy name="portal">
<authentication>
<login-module code="org.jboss.security.auth.spi.LdapLoginModule" flag="required">
<module-option name="java.naming.factory.initial">
com.sun.jndi.ldap.LdapCtxFactory
</module-option>
<module-option name="java.naming.provider.url">
ldap://localhost/
</module-option>
<module-option name="java.naming.security.authentication">
simple
</module-option>
<module-option name="java.naming.security.principal">
cn=Manager,dc=example,dc=com
</module-option>
<module-option name="java.naming.security.credentials">
secret
</module-option>
<module-option name="principalDNPrefix">cn=</module-option>
<module-option name="principalDNSuffix">
,ou=people,dc=example,dc=com
</module-option>
<module-option name="password-stacking">useFirstPass</module-option>
<module-option name="rolesCtxDN">
ou=groups,dc=example,dc=com
</module-option>
<module-option name="uidAttributeID">member</module-option>
<module-option name="matchOnUserDN">true</module-option>
<module-option name="roleAttributeID">cn</module-option>
<module-option name="roleAttributeIsDN">false </module-option>
<!--
<login-module code="org.jboss.portal.identity.auth.IdentityLoginModule" flag="required">
<module-option name="unauthenticatedIdentity">guest</module-option>
<module-option name="userModuleJNDIName">java:/portal/UserModule</module-option>
<module-option name="roleModuleJNDIName">java:/portal/RoleModule</module-option>
<module-option name="additionalRole">Authenticated</module-option>
<module-option name="password-stacking">useFirstPass</module-option>
-->
</login-module>
</authentication>
</application-policy>
</policy>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 5 months