-
Suggestion
-
Resolution: Won't Do
-
* Mac OS X
* JIRA 5.0.6
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Current it's possible to enter a user object filter or group object filter that exceeds the limitations of the database schema cwd_directory_attribute.attribute_value is a varchar(255). Can you look at adding this limitation into the JIRA GUI to prevent users from encountering a data truncation error in the logs? For example:
... Caused by: com.atlassian.crowd.embedded.ofbiz.db.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:DirectoryAttribute][directoryId,10100][name,ldap.user.filter][value,(&(objectclass=unicornRider)(!(ou:dn:=Guardians of The Globe))(|(memberof=cn=Lightning Strike Thunderdome,ou=Groups,ou=The Avengers)(memberof=cn=jiradmins,ou=Groups,ou=The Avengers)(memberof=cn=strikeforceone,ou=Groups,ou=The Avengers)(memberof=cn=UAT,ou=Groups,ou=The Avengers)(memberof=cn=myspace,ou=Groups,ou=The Avengers))] (SQL Exception while executing the following:INSERT INTO cwd_directory_attribute (directory_id, attribute_name, attribute_value) VALUES (?, ?, ?) (Data truncation: Data too long for column 'attribute_value' at row 1)) ...
To replicate
- Add a new User Directory to JIRA.
- Add a very long object or group filter.
- Attempt to synchronise, this will fail with a "Data truncation" error.
Workaround
Please refer to the Data Truncation due to Data too long for column KB article.
- is related to
-
- Closed
- relates to
-
JRACLOUD-13329 Error when adding a group with name longer than 60 characters to a notification scheme: too long for database column
-
- Short Term Backlog
-