ProfileAPI: Validation for ID should be unified

Found in

EPiServer.Profiles.Client 1.6.0

Fixed in

EPiServer.Profiles.Client 1.6.0

(Or a related package)

Created

Aug 15, 2018

Updated

Sep 18, 2018

State

Closed, Fixed and tested

Description

Steps to reproduce

1. PUT a profile with ID=@, $, Slash , Backslash (
), Asterisk , Question mark, Less than (<), Greater than (>), Vertical bar (|), Space ( ), Comma(,)
PUT urlProfileAPI/@
--> 400 Bad Request returns with
{
"error":

{ "code": "400", "message": "Invalid profileId, profileId only supports 0-9,A-Z,a-z,- character and must start with number or letter.", "target": "", "details": [] }

}

2. PUT segment with ID=@
PUT urlSegments/@
--> 400 Bad Request returns

3. PUT scope with ID=@
PUT urlScopeAPI/@
--> 200 OK returns, a new scope is created with

{ "ScopeId": "@", "Description": null }

Expected: --> 400 Bad Request returns with
{
"error":

{ "code": "400", "message": "Invalid scopeId, profileId only supports 0-9,A-Z,a-z,- character and must start with number or letter.", "target": "", "details": [] }

}