[HELP-6964] FIWARE.Request.Tech.Security.AuthorizationPDP.Securing verbs via the PEP proxy - JIRA

Fernando Lopez made changes - 27/May/21 10:54 AM

Fix Version/s

2021 [ 12600 ]

Fernando Lopez made changes - 24/Sep/19 9:36 AM

Description

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?

--

*****

Lageweg 2 3703 CA Zeist
■ *mob *+31(0) 6 45 372 363
■ *tel* +31(0)30 699 70 20
■ *mail* *****

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@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-tech-help mailing list
Fiware-tech-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-tech-help

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?