Accessing different annonymous content based on url alias

[Former Member]

Hi everyone, hope you can help me.

I got portal running on our intranet, users have annonymous access to

portal content, but now I want users to access different anon content based

on the url.

So basically this is what I did:

(1) created users on UME, each one assigned to a different role with their

own content:

looks like:

user_anon1 - rl_anon_cont1

user_anon2 - rl_anon_cont2

and so on

(2) in the J2EE Engine Config Tool, added all those users into ume.login.guest_user.uniqueids

so they are assigned to portal annonymous group

(3) created url alias into web.xml and restarted portal

However, this has nothing to do with authentication yet, I want to when an user

types on their browser the portal url http://host:port/irj/alias1 the portal to login as

user_anon1 and when user types http://host:port/irj/alias2 the user_anon2 login.

Where/What should I work to achieve that?

thanks in advance,

rafael

Edited by: Rafael Martins on Jan 28, 2009 10:05 AM

[abdulbasit · Accepted solution]

Hi,

Try to logon Portal with URL :

/irj/portal/anonymous?guest_user=user_anon1

and

/irj/portal/anonymous?guest_user=user_anon2

Remember that, when the user first open the anon1 page and in the same browser tries to open anon2 page there will be user switch problem. If that case exist I suggest you use different domain names. For example

http://anon1.mydomain.com/irj/portal/anonymous?guest_user=user_anon1

and

http://anon2.mydomain.com/irj/portal/anonymous?guest_user=user_anon1

If that's not possible you have to write custom java / javascript programs to handle this case...

[Former Member · Accepted solution]

Hello, I've tried that and with both entries I access the role assigned to user1,

I guess I missed some java implementation that handles this parameter (guest_user),

but that's the problem, I don't know what file handles this first client request

[abdulbasit · Accepted solution]

Hi Rafael,

You do not need implementation for guest_user parameter. This is standard parameter. Did you tried both entries on the same browser window? Could you first close the browser and try to go user2 with newly opened browser window...

When you open with parameter user1; then user1 is automatically logged on and mysapsso2 cookie is created. After this point, even ypu change url to user2 since user1 is already logged on and mysapsso2 is created for user1 you cannot switch to user2 and you see the page for user1.

I had the same problem and tried lots of different alternatives. I strongly suggest you use different subdomain for each user.

http://user1.mydomain.com/irj/portal/anonymous?guest_user=user1

http://user2.mydomain.com/irj/portal/anonymous?guest_user=user2

Since you use this on intranet, you should easily point all this domains to the portal server.

Otherwise you need custom program to delete cookie, and handle logged on user, querystring etc. When client uses IE7 of FF with multiple tabs you need to handle each tab separetly since all tabs shares the same session...

Hope this helps...

Abdul.

[Former Member · Accepted solution]

Hello Abdul, thanks for the response, you misunderstood me about the guest_user

thing, what I am seeking is the component that handles the user passed as parameter,

some class must receive the data (user anon1 or anon2 in this case) and then

log on that user (maybe a file like portalapp.xml or index.jsp)

And yes, I tried with diferent windows, also cleared cache, unfortunatelly changing the

domain isn't an option to me (internal policies). I'm gonna look around all the path the

request pass until logon and try to find something...

thanks,

Rafael

[abdulbasit · Accepted solution]

Hi Rafael,

As I said before you don't need to handle the user coming from parameter guest_user. This is standart parameter and Portal handles this automatically.

You can see the explanation :

http://help.sap.com/saphelp_nw04s/helpdata/en/1e/e19f58136e654d9709befa464314f2/content.htm

By default, users are logged on as the first user in the list of anonymous users in ume.login.guest_user.uniqueids. Optionally, you can define that a specific anonymous user be used to access the portal in anonymous mode by defining the guest_user parameter in the portal URL.

In the following example, the portal is accessed with the anonymous user anon2:

<http/https>://<server>:<port>/irj/portal/anonymous?guest_user=anon2

Your problem seems to be different... If you configured users correctly you should have access to anon2 user with parameter guest_user=anon2.

If you solve this problem we can go further to find an alternative way of using different subdomains. But first you should be able to access anon2 with

<http/https>://<server>:<port>/irj/portal/anonymous?guest_user=anon2

Regards

Abdul.