[Fiware-tech-help] [FIWARE-JIRA] (HELP-6964) FIWARE.Request.Tech.Security.AuthorizationPDP.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 k.patenaude at itude.com : 

Just to be sure:
Do we need to configure a Wilma PEP proxy and specify the Authorization PDP
GE URL in the config file? We are only configuring IDM with the AuthZForce
service.
Because we don't specific a our AuthZForce domain maybe the system doesn't
know where to write the policy? I saw that we do have to define this in the
PEP config file if we were to use this in combination with IDM and the
AuthZForce service.

Met vriendelijke groet/Kind regards,

*Kirstie Patenaude*
Mobile Software Engineer

HNK-CS
Arthur van Schendelstraat 650
3511 MJ Utrecht

■ *Mob:* +31(0)6 51 13 56 18
■ *Tel. receptie:* +31(0)30 699 70 20
■ *Mail:* k.patenaude at itude.com

www.itude.com ■ K.v.K. 30146090

On Tue, Sep 20, 2016 at 4:51 PM, Kirstie Patenaude <k.patenaude at itude.com>
wrote:

> I linked a permission to a role and clicked on save to generate the
> rule/policy but do not see what you describe in my logs (these are the logs
> we previously sent up).
> I do see:
> ACCESS_CONTROL_MAGIC_KEY setting is not set.
> WARNING:idm_logger:ACCESS_CONTROL_MAGIC_KEY setting is not set.
>
> Met vriendelijke groet/Kind regards,
>
> *Kirstie Patenaude*
> Mobile Software Engineer
>
> HNK-CS
> Arthur van Schendelstraat 650
> 3511 MJ Utrecht
>
> ■ *Mob:* +31(0)6 51 13 56 18
> ■ *Tel. receptie:* +31(0)30 699 70 20
> ■ *Mail:* k.patenaude at itude.com
>
> www.itude.com ■ K.v.K. 30146090
>
> On Tue, Sep 20, 2016 at 2:56 PM, Help-Desk <jira-help-desk at fi-ware.org>
> wrote:
>
>>
>>
>



> FIWARE.Request.Tech.Security.AuthorizationPDP.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: Alvaro Alonso
>         Attachments: 2016-09-05 08_57_48.486 21 INFO eventlet.wsgi.txt, image001_01D21293559CAF30.png, Logs IDM_Horizon after creating permission_HTTP.txt rule in IDM, ParseError at _idm_myApplications_fdae7d987c6a435188a2200e31cac4db_edit_roles_.html, PastedGraphic-2.png, PastedGraphic-2.png, PastedGraphic-2.png, PastedGraphic-2.png, PastedGraphic-2.png, PastedGraphic-2.png, PastedGraphic-2.png, 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)