Bug 94 - specify different authentication requirements for each transport
Summary: specify different authentication requirements for each transport
Status: NEW
Alias: None
Product: repro
Classification: Unclassified
Component: proxy (show other bugs)
Version: unspecified
Hardware: All All
: P1 enhancement
Assignee: Owner of all unassigned bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-11 13:41 CDT by Daniel Pocock
Modified: 2015-08-11 13:41 CDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Pocock 2015-08-11 13:41:03 CDT
When multiple advanced transport definitions are used, it may be useful to specify different authentication requirements for each of them.

For example, on a TLS transport, it may be that one of client certificate or DIGEST is acceptable (both not required) whereas on a WebSocket over TLS (WSS) transport, it may be preferred to use the WebSocket cookie auth and not accept DIGEST at all.