You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Eoghan Glynn (JIRA)" <ji...@apache.org> on 2007/02/22 17:59:05 UTC
[jira] Created: (CXF-431) Extend AuthorizationPolicy to include
realm and targetURI
Extend AuthorizationPolicy to include realm and targetURI
---------------------------------------------------------
Key: CXF-431
URL: https://issues.apache.org/jira/browse/CXF-431
Project: CXF
Issue Type: Sub-task
Reporter: Eoghan Glynn
Assigned To: Eoghan Glynn
Extend the AuthorizationPolicy schema to allow for multiple authoziation instances, each including new Realm and TargetURI elements in addition to the existing UserName, Password, AuthorizationType etc. This would restrict the creds to be handed out only in response to a challenge from a specific target URI, when the challenge refers to a specific realm.
If the UserName and Password are not explicitly configured for a particular realm/targetURI, then the application trust evaluation callback may provide these dynamically.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-431) Extend AuthorizationPolicy to include
realm and targetURI
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-431.
-----------------------------
Resolution: Fixed
Fix Version/s: (was: 2.1)
2.0.1
> Extend AuthorizationPolicy to include realm and targetURI
> ---------------------------------------------------------
>
> Key: CXF-431
> URL: https://issues.apache.org/jira/browse/CXF-431
> Project: CXF
> Issue Type: Sub-task
> Components: Transports
> Affects Versions: 2.0-RC
> Reporter: Eoghan Glynn
> Assignee: Eoghan Glynn
> Fix For: 2.0.1
>
>
> Extend the AuthorizationPolicy schema to allow for multiple authoziation instances, each including new Realm and TargetURI elements in addition to the existing UserName, Password, AuthorizationType etc. This would restrict the creds to be handed out only in response to a challenge from a specific target URI, when the challenge refers to a specific realm.
> If the UserName and Password are not explicitly configured for a particular realm/targetURI, then the application trust evaluation callback may provide these dynamically.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-431) Extend AuthorizationPolicy to include
realm and targetURI
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Diephouse updated CXF-431:
------------------------------
Fix Version/s: (was: 2.0-RC)
2.1
Moving these issues to 2.1 as I don't think we'll get them for 2.0. Feel free to switch reschedule if you feel appropriate.
> Extend AuthorizationPolicy to include realm and targetURI
> ---------------------------------------------------------
>
> Key: CXF-431
> URL: https://issues.apache.org/jira/browse/CXF-431
> Project: CXF
> Issue Type: Sub-task
> Components: Transports
> Affects Versions: 2.0-RC
> Reporter: Eoghan Glynn
> Assigned To: Eoghan Glynn
> Fix For: 2.1
>
>
> Extend the AuthorizationPolicy schema to allow for multiple authoziation instances, each including new Realm and TargetURI elements in addition to the existing UserName, Password, AuthorizationType etc. This would restrict the creds to be handed out only in response to a challenge from a specific target URI, when the challenge refers to a specific realm.
> If the UserName and Password are not explicitly configured for a particular realm/targetURI, then the application trust evaluation callback may provide these dynamically.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-431) Extend AuthorizationPolicy to include
realm and targetURI
Posted by "Bozhong Lin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bozhong Lin updated CXF-431:
----------------------------
Component/s: Transports
Fix Version/s: 2.0-RC
Affects Version/s: 2.0-RC
> Extend AuthorizationPolicy to include realm and targetURI
> ---------------------------------------------------------
>
> Key: CXF-431
> URL: https://issues.apache.org/jira/browse/CXF-431
> Project: CXF
> Issue Type: Sub-task
> Components: Transports
> Affects Versions: 2.0-RC
> Reporter: Eoghan Glynn
> Assigned To: Eoghan Glynn
> Fix For: 2.0-RC
>
>
> Extend the AuthorizationPolicy schema to allow for multiple authoziation instances, each including new Realm and TargetURI elements in addition to the existing UserName, Password, AuthorizationType etc. This would restrict the creds to be handed out only in response to a challenge from a specific target URI, when the challenge refers to a specific realm.
> If the UserName and Password are not explicitly configured for a particular realm/targetURI, then the application trust evaluation callback may provide these dynamically.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.