[overlord-issues] [JBoss JIRA] (SRAMP-395) S-RAMP allows artifacts to be created with invalid characters in the Artifact Type

Eric Wittmann (JIRA) issues at jboss.org
Tue Apr 8 07:44:12 EDT 2014


     [ https://issues.jboss.org/browse/SRAMP-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Wittmann updated SRAMP-395:
--------------------------------

    Description: 
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.

  was:
There are two ways (I believe) that users can mistakenly create artifacts with an invalid artifact type.  The first is via the CLI:

s-ramp:upload /path/to/file.ext "Invalid Type"
s-ramp:create "Invalid Type"

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.


    
> 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: David virgil naranjo
>             Fix For: 0.5.0 - API Management
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the overlord-issues mailing list