Extranet access

[Former Member]

Hello together,

Do you know any documents / help for building a extranet access to the portal?

Did you already implement an extranet access? How did you proceed?

Thanks in advance for any any help.

Regards,

Stefan

Message was edited by: Stefan Kuster

Changed title

[Former Member]

Hi,

Did u mean implementing external facing portal,if so

the following url might be helpful.check this out.

http://help.sap.com/saphelp_nw04s/helpdata/en/04/e5b7c3de384515afeafa0dab8e44e0/frameset.htm

Rgds,

Santhosh

[Former Member]

Hello Santhosh,

Hmm, I'm not really sure if this is what I'm looking for.

I mean an external access (with username & password) for customers, etc through the portal in the internet.

Customers, suppliers should have access to specific WebDynpro's for having access to R/3 content in "realtime".

Regards,

Stefan

[Former Member]

Does your company already have a DMZ? If so, place a proxy server there and your customers will be able to access your portal from there.

[Former Member]

Yes we have a DMZ. There is an Apache with reverse proxy running.

Fact is, it is running and we have over the internet an https access to our portal.

But I'm looking for a "good" How-To guide for the implementation and configuration of the proxy / apache / or what else.

We created a extranet logon group in the User Administration for e.g. customers. In the master rule collection we defined a special portal desktop with only their rules.

Problem whith this configuration is, that every internal user can also logon through the extranet (unfortunately also the admin users).

Can for e.g. the access for admin users be excluded from login over the extranet?

So you see, I'm looking for a complete all in one help...

Stefan

[Former Member]

What are you doing for an LDAP?

[Former Member]

No LDAP - only Portal Database. All users are defined in the portal database.

[Former Member]

All internal users and also the customers for the extranet. The customers are in a special extranet user group for route them to another portal desktop.

[Former Member]

I have no idea on where to get good apache resources.

To restrict access based on groups is one thing, but you needs a solution that is based on the network they are coming from.

[Former Member]

Is this only an apache issue? Can the access be controlled only in the apache and not in the portal?

Would it make any difference if we used LDAP? How would it work there?

[Former Member]

At first it didn't click with me that you don't want internal users to use the portal over the internet.

No, LDAP would not make a difference.

I know will IIS you can set up the site for user name and password, I am not sure with Apache.

[Former Member]

Internal users are ok to logon over the internet. I would like to block "admin"-users to logon over the internet.