[overlord-issues] [JBoss JIRA] (SRAMP-395) S-RAMP allows artifacts to be created with invalid characters in the Artifact Type
RH Bugzilla Integration (JIRA)
issues at jboss.org
Thu Jul 24 10:47:32 EDT 2014
[ https://issues.jboss.org/browse/SRAMP-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987763#comment-12987763 ]
RH Bugzilla Integration commented on SRAMP-395:
-----------------------------------------------
Rick Wagner <rwagner at redhat.com> changed the Status of [bug 1114732|https://bugzilla.redhat.com/show_bug.cgi?id=1114732] from POST to ON_QA
> S-RAMP allows artifacts to be created with invalid characters in the Artifact Type
> ----------------------------------------------------------------------------------
>
> Key: SRAMP-395
> URL: https://issues.jboss.org/browse/SRAMP-395
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 0.4.0 - Tomcat Support
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.5.0.Alpha1, 0.5.0
>
>
> There are two ways (I believe) that users can mistakenly create artifacts with an invalid artifact type. The first is via the CLI:
> {code}
> s-ramp:upload /path/to/file.ext "Invalid Type"
> s-ramp:create "Invalid Type" "Valid Artifact Name" "Description goes here."
> {code}
> The other is via the s-ramp UI's Import Artifact dialog. This dialog allows the user to type in any Artifact Type they want, which is an opportunity to mess it up.
> We need to make sure we have appropriate validation of any custom Artifact Type provided by the user on the server (probably in the REST layer).
> For bonus points we can add validation to the UI and CLI to prevent the request from even being made to the server unless it's valid.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
More information about the overlord-issues
mailing list