Ticket #139 (closed enhancement: fixed)
Allow security by token
Reported by: | jayftee | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 1.4dev |
Component: | zoo-kernel | Version: | 1.0 |
Keywords: | security token | Cc: |
Description
It would be nice if Zoo incoming request header values can be passed on in the data gathering requests.
By example, if an incoming request's header contains: SecurityToken?=ASDGARSGFABDAGRSGW$!$WGW, then, all requests to downstream WFS services would have the value of the SecurityToken? added to the header of the outgoing request.
Now, obviously, a specific prefix for the variables would be required because we do no need nor want all header variables to be passed on so, something like ZooSecurityToken?, or ZooWhateverMyVariableNameIs? would be valid.
With this, someone that uses a security via tokens can secure Zoo.
This idea is to cicumvent the fact Zoo does not allow impersonation to take place so that, incoming credentials are passed thru to outgoing requests.