Persitence API Permissions for NON Java App

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Persitence API Permissions for NON Java App

bruno.buzzi
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

Re: Persitence API Permissions for NON Java App

Erik Bruchez
Administrator
Bruno,

The headers (Orbeon-Username, etc.) should be passed whether the persistence implementation is implemented Java or not. If they are not, it is a bug.

This said, we have made some changes as recently as 4.9 regarding the handling of headers:

    https://github.com/orbeon/orbeon-forms/issues?utf8=%E2%9C%93&q=milestone%3A4.9+header

So it might be something that has been fixed already, or who knows, this particular scenario might still not be handled properly.

-Erik
Reply | Threaded
Open this post in threaded view
|

Re: Persitence API Permissions for NON Java App

bruno.buzzi
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

Re: Persitence API Permissions for NON Java App

bruno.buzzi
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

Re: Persitence API Permissions for NON Java App

Erik Bruchez
Administrator
Bruno,

Good. And are you getting the authentication headers when outside of Form Builder?

-Erik
Reply | Threaded
Open this post in threaded view
|

Re: Persitence API Permissions for NON Java App

bruno.buzzi
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

Re: Persitence API Permissions for NON Java App

Erik Bruchez
Administrator
Bruno,

> In this case i will need the user and roles in the Headers to apply and additional filter.
I suspect that this can not be done when using "container" authentication only with "headers" authentication will work (not sure about this ! but i will investigate). If this is the case then my persistence layer will support permission only with authentication with "headers". As i said i need to investigate a little more.

Whether using container or headers, the idea is that the Orbeon-Username, Orbeon-Roles and Orbeon-Group headers should be set by and passed to the persistence layer. If that's not the case we should fix it.

-Erik
Reply | Threaded
Open this post in threaded view
|

Re: Persitence API Permissions for NON Java App

bruno.buzzi
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

Re: Persitence API Permissions for NON Java App

bruno.buzzi
CONTENTS DELETED
The author has deleted this message.