[Fiware-tech-help] [FIWARE-JIRA] (HELP-6964) Securing verbs via the PEP proxy

[FW External User (JIRA)]

     [ https://jira.fiware.org/browse/HELP-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

FW External User updated HELP-6964:
-----------------------------------

Comment by aalonsog at dit.upm.es : 

Hi, 

you should contact the AuthZForce owner to solve those questions. I’ve just assigned the corresponding issue to him so he will contact you soon. 

BR
--
Álvaro

> El 25 jul 2016, a las 16:57, Coen Houtman <c.houtman at itude.com> escribió:
> 
> Dear Sir/Madam,
> 
> We are really struggling to secure the ContextBroker to prevent DELETE calls. So much that this has become an impediment to successfully finish our sprint. As Scrum master of this team I would like to ask you kindly to respond to the e-mail below. An indication of when we can expect a response would also really be helpful. 
> 
> We look forward to your response.
> 
> Kind regards,
> 
> On Fri, Jul 22, 2016 at 10:35 AM Cristan Meijer <c.meijer at itude.com <mailto:c.meijer at itude.com>> wrote:
> Hello,
> 
> We would like to secure out ContextBroker so POSTS are allowed, but a DELETE isn't. We've asked you about this and you've said we should do the following:
> 
> * You can configure as many PEPs as you want. You have only to modify the listening port.
> * You can configure an AuthZForce in https://github.com/ging/horizon/blob/master/openstack_dashboard/local/local_settings.py.example#L629 <https://github.com/ging/horizon/blob/master/openstack_dashboard/local/local_settings.py.example#L629>. You only need to configure the URL in which it is listening
> * To configure PEP to work with AuthZForce you have to use the Level 2 of security. Here you will find tutorials about this: https://edu.fiware.org/course/view.php?id=131 <https://edu.fiware.org/course/view.php?id=131>
> We've tried this, but we've had the following problems:
> If we pull the docker image of fiware/authzforce-ce-server:release-5.4.0 or release-5.3.0a, the image starts, but shuts down after a few seconds after which the logs state that tomcat 7 can't be started.
> When we run fiware/authzforce-ce-server:release-4.4.1b, we get a tomcat with no webapp in the webapps directory other than the default stuff. 
> Performing a manual installation using this guide <http://authzforce-ce-fiware.readthedocs.io/en/release-5.3.0a/InstallationAndAdministrationGuide.html#installation> will have the same result.
> In your previous mail, it is stated that we need AuthZForce. However, Keypass seems to do something similar. Can you explain the difference?
> 
> Can you help us with this?
> 
> -- 
> Cristan Meijer
> Software engineer
> 
> <PastedGraphic-2.png>  
> Lageweg 2 3703 CA Zeist   
> ■ mob +31(0) 6 45 372 363  
> ■ tel 	+31(0)30 699 70 20  
> ■ mail c.meijer at itude.com <mailto:c.meijer at itude.com>
> 
> www.itude.com <http://www.itude.com/> ■ K.v.K. 30146090
>



> [Fiware-tech-help] Securing verbs via the PEP proxy
> ---------------------------------------------------
>
>                 Key: HELP-6964
>                 URL: https://jira.fiware.org/browse/HELP-6964
>             Project: Help-Desk
>          Issue Type: extRequest
>          Components: FIWARE-TECH-HELP
>            Reporter: FW External User
>            Assignee: Cyril Dangerville
>         Attachments: PastedGraphic-2.png, PastedGraphic-2.png, PastedGraphic-2.png
>
>
> Hello,
> We would like to secure out ContextBroker so POSTS are allowed, but a
> DELETE isn't. We've asked you about this and you've said we should do the
> following:
> * You can configure as many PEPs as you want. You have only to modify the
> > listening port.
> > * You can configure an AuthZForce in
> > https://github.com/ging/horizon/blob/master/openstack_dashboard/local/local_settings.py.example#L629.
> > You only need to configure the URL in which it is listening
> > * To configure PEP to work with AuthZForce you have to use the Level 2 of
> > security. Here you will find tutorials about this:
> > https://edu.fiware.org/course/view.php?id=131
> We've tried this, but we've had the following problems:
>    - If we pull the docker image of
>    fiware/authzforce-ce-server:release-5.4.0 or release-5.3.0a, the image
>    starts, but shuts down after a few seconds after which the logs state that
>    tomcat 7 can't be started.
>    - When we run fiware/authzforce-ce-server:release-4.4.1b, we get a
>    tomcat with no webapp in the webapps directory other than the default
>    stuff.
>    - Performing a manual installation using this guide
>    <http://authzforce-ce-fiware.readthedocs.io/en/release-5.3.0a/InstallationAndAdministrationGuide.html#installation>
> will
>    have the same result.
> In your previous mail, it is stated that we need AuthZForce. However,
> Keypass seems to do something similar. Can you explain the difference?
> Can you help us with this?
> -- 
> *Cristan Meijer*
> Software engineer
> Lageweg 2 3703 CA Zeist
> ■ *mob *+31(0) 6 45 372 363
> ■ *tel*  +31(0)30 699 70 20
> ■ *mail* c.meijer at itude.com
> www.itude.com ■ K.v.K. 30146090
> _____________________________________________________________________________
> ****Op deze mail is een disclaimer van toepassing. De inhoud daarvan is te
> lezen op onze website****
> Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
> Please, send your messages using the new domain (Fiware-tech-help at lists.fiware.org) instead of the old one.
> _______________________________________________
> Fiware-tech-help mailing list
> Fiware-tech-help at lists.fiware.org
> https://lists.fiware.org/listinfo/fiware-tech-help
> [Created via e-mail received from: Cristan Meijer <c.meijer at itude.com>]



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)