You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Woonsan Ko (JIRA)" <je...@portals.apache.org> on 2010/03/29 17:34:27 UTC

[jira] Assigned: (JS2-1129) JetSpeed hides error if values in SSO-Portlets are specified too long

     [ https://issues.apache.org/jira/browse/JS2-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Woonsan Ko reassigned JS2-1129:
-------------------------------

    Assignee: Woonsan Ko

> JetSpeed hides error if values in SSO-Portlets are specified too long
> ---------------------------------------------------------------------
>
>                 Key: JS2-1129
>                 URL: https://issues.apache.org/jira/browse/JS2-1129
>             Project: Jetspeed 2
>          Issue Type: Bug
>          Components: Security
>    Affects Versions: 2.2.0
>            Reporter: Dominik Stadler
>            Assignee: Woonsan Ko
>            Priority: Critical
>
> I am trying to use the "SSO Web Content" Portlet to display a website which requires basic authentication. Although all the parameters are specified correctly, I get the error "Could not add remote user: portal principal admin is already associated with a remote user for this site!" displayed when I save the portlet configuration.
> I found out that actually there is a SQL Exception during writing the configuration, but the code just prints out this incorrect error message. Also log-output does not contain any hint of the actual problem.
> Doing some tracing, I found that the problem is caused by the following commit: http://mail-archives.apache.org/mod_mbox/portals-jetspeed-dev/200905.mbox/%3C20090501033954.14ADF23888A4@eris.apache.org%3E
> Look at SSOWebContentPortlet.java, line 194: The change replaces the "throw" of the actual exception with the dumb error message which effectively hides the actual cause in this case. In my case the error was "Unexpected security error at JetspeedSecurityPersistenceManager from addDomain: OJB operation; SQL []; A truncation error was encountered trying to shrink VARCHAR 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' to length 30.; nested exception is java.sql.SQLDataException: A truncation error was encountered trying to shrink VARCHAR 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' to length 30.
> Please adjust the error-check here to only report the error text if this is the actual cause and report the actual error otherwise.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org