Tell me more ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.
up vote 0 down vote favorite

I have a web part which I am trying to target to a specific audience (the 'Staff' audience.)

I have the web part in the home page of a site that has anonymous access enabled.

I have set the Target Audience of the webpart to 'Staff'. The idea is that anonymous viewers can't see the web part, but logged-in members of staff can see the webpart.

This works fine, as long as I am browsing the site from the server on which SharePoint is running, using the internal domain name (e.g. http://localhost:5050/site). If I view the site home page while not logged in, I can't see the webpart -- this is the correct behaviour.

However, if I view the site via the public address (e.g. http://www.realaddress.co.uk:5050/site) while not logged in, I can see the webpart. (I shouldn't be able to -- it's only targeted at the 'Staff' audience'.) This happens if I'm browsing either on the SharePoint server or a remote machine.

I'm a bit baffled!

share|improve this question

1 Answer

up vote 2 down vote

Are the external zone just an alternate access mapping (AAM) or is it an extended web app (new zone) with other authentification?

share|improve this answer
I hadn't heard of alternate access mapping before, so hadn't even set one up -- if I look at the mapping, my internal URL is the same as the public URL for the zone -- i.e. Internal URL = internal:5050 and Public URL = internal:5050 . Obviously that doesn't look right so you've probably hit the problem, thanks! I'm not able to test changing the URLs just yet, but will give it a try later. Thanks for the tip. – ngm Jun 17 '10 at 8:36

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.