Web Dispatcher for Producer & Consumer Portal

[Former Member]

Hi

We have web dispatcher 7.20 (Patch 85 - latest), our web dispatcher is configured to call our consumer portal (in our federated portal network).

We have connected 3 producer portals to our consumer portal.

So now when users from external world calls our web dispatcher thru a URL, say : https://externaluser.domain.com

it points to our consumer portal.

We have two questions

1. Can the external users view our producter portal content also from the external by logging into our consumer portal (since ours is a federated portal network), if so what kind of configurations has to be maintained in web dispatcher/firewall other than the current consumer portal configuration.

2. Since our BW portal is also published in our consumer portal, We need to block our BW content for the external users, only users who logs thru VPN or internal network alone, should view our BW reports, how can we handle this?

Thanks & Regards

Senthil

[Former Member · Accepted solution]

Hello Senthil,

What I understand is your Consumer portal takes data from producer portal as well as your BW system.

Unless there is a provision on your consumer portal to see the data of producer protal or BW I hope users will not be able to see any data.

One more thing is do you have any iviews on the portal which carries data of producer portal as well as BW system?

If you do and if the users have access to that part of the portal then they will be exposed else I hope it will not be.

Regards

Vivek

[Former Member · Accepted solution]

Thank you Vivek.

Yes we have iviews in our consumer portal, which refers to our consumer portal and BW system.

All our users are assigned relevant roles to view those iviews, our question is how to restrict our users not to view BW system if they login externally (from internet). The same users if they login thru VPN or from our office internal network they should be able to view our BW reports.?

Regards

Senthil

[Former Member · Accepted solution]

Hello Sethil,

Again you can restrict them using the authorization objects and create seperate roles for the external users and seperate for internal.

Allow the objects to be part of internal users where as for external remove those objects which will automatically restrict the external users by accessing them.

Regards

Vivek