[
https://issues.apache.org/activemq/browse/SM-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trudi Ersvaer updated SM-1897:
------------------------------
Attachment: groups.properties
security.xml
SM-1897-sa.zip
Attached is a service assembly that I've created that should replicate this
issue.
Attached is also security.xml which shows the authZ entry value.
user-passwords.properties has: trudi=password
> 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
> Attachments: groups.properties, security.xml, SM-1897-sa.zip,
> users-passwords.properties
>
>
> 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.
