[jira] Resolved: (SM-1897) authorizationEntry service namespace can't be a urn

["Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>]

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

Jean-Baptiste Onofré resolved SM-1897.
--------------------------------------

    Resolution: Fixed

> authorizationEntry service namespace can't be a urn
> ---------------------------------------------------
>
>                 Key: SM-1897
>                 URL: https://issues.apache.org/activemq/browse/SM-1897
>             Project: ServiceMix
>          Issue Type: Bug
>    Affects Versions: 3.3.1
>         Environment: Windows XP Pro.
> Java 1.6.0_12
>            Reporter: Trudi Ersvaer
>
> In security.xml the authorizationEntry's service attribute seems not to cope with a urn namespace.
> For example, I've replaced the existing authorization entry (in security.xml) with a new one:
> service="{urn:/addsource.wsdl}:addsourceService" roles="superuser"
> The problem with this is that I get a PatternSyntaxException because the service name is translated into (I can see this in the debugger):
> {{urn}/addsource.wsdl}:addsourceService  
> When I removed the braces from the service name in security.xml for example: 
> service="urn:/addsource.wsdl:addsourceService" roles="superuser"
> the service still doesn't match because the service name is transated into (again viewed in the debugger): 
> {urn}/addsource.wsdl:addsourceService
> If I change all my namespaces to:
> xxx
> and in security.xml changed the service name to:
> xxx:addsourceService
> finally the service matched and authZ works.
>  
> Any ideas why the authorizationEntry isn't coping with a urn namespace?

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