Opened 12 years ago

Closed 12 years ago

#888 closed enhancement (fixed)

Possibility for allowing the public_user to use owsproxy services

Reported by: armin11 Owned by: armin11
Priority: major Milestone: 2.7.4 release
Component: core Version: 2.7.3
Keywords: owsproxy, security, public_user Cc:

Description

Normaly the services which are secured by the mapbender owsproxy cannot be accessed by a public_user. When an owsproxy url is given away thru metadata (maybe for inspire) the dynamically build url will time out and no one can use it any more. To overcome this behavior, the owsproxy module has to be altered in such a way, that a public user - whose id maybe defined in mapbender.conf - is able to use a owsproxy resource for which the authorization is given. Also signed in user should be able to use owsproxy urls which are timed out! The session id should be refreshed and the authorization should be checked again the new session.

Change History (1)

Note: See TracTickets for help on using tickets.