ws-muse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kam K. Yee (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MUSE-242) Security model
Date Mon, 07 Apr 2008 14:35:24 GMT

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

Kam K. Yee updated MUSE-242:
----------------------------

    Attachment: muse-242.zip

Attached is the implementation of this new feature contributed by the IBM Team.

> Security model
> --------------
>
>                 Key: MUSE-242
>                 URL: https://issues.apache.org/jira/browse/MUSE-242
>             Project: Muse
>          Issue Type: New Feature
>          Components: Core Engine - Routing and Serialization
>            Reporter: Balan Subramanian
>            Assignee: Dan Jemiolo
>             Fix For: 2.3.0
>
>         Attachments: muse-242-design1.0.pdf, muse-242.zip
>
>
> Muse support for WS-Security for credentials transport is desired. Similar to the way
a persistence class can be assigned to a capability or a resource type we must be able to
assign a security class that will handle the actual authentication using mechanisms like JAAS
or directly on LDAP or OS password store. The encryption of the credentials also needs to
be considered. This will have implications on code generation and client side code as well
in addition to the endpoint code itself. This is a better way to provide authentication than
using HTTPS and this allows the granularity of authentication at the capability level.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org


Mime
View raw message