Re: MOSS My Sites for non-AD users

Hi Steven,
I am currently looking at ways of setting up authentication for my
sites. We want to use FBA, and I have tried LDAP and AD providers. At
the moment, I am using the AD provider as our AD/LDAP doesn't allow
anonymous binds and I can't find a way of passing credentials to the
LDAP provider. If I took your LDAP provider,
(http://www.sharepointblogs.com/helloitsliam/archive/2006/08/15/10066.aspx
comments) I could adapt it and add my own credentials to the call, with
your permission....
With the AD provider, there doesn't seem to be a way of linking
profiles imported with the AD import to accounts created with the
ADMembership provider. Is that what you found?
At the moment, we need to use FBA, and we need to have
personalisation/MySites, and what you describe here is the only way I
have found described that will support this.
Thanks
Mark


steven@xxxxxxxxxxxxxxxxx wrote:
I've successfully create a custom LDAP membership provider for use on
our main web application. LDAP was used as a custom source for
importing profiles. By mapping uid from ldap to username in both the
custom provider and the profile import, sharepoint can associate users
to their profiles. In doing so our main site uses the displayname from
the profile even thou the person authenticated from the custom
provider.

From these ldap account I am able to create mysites. However because
mysites are hosted by a Share Services Provider it too needs to use
your custom membership provider.

At the current time I use AD to authenticate users access to the LDAP
MySites. Thing is, is you click MySite, you then have an AD MySite
created.

Check out my BLOG for more information http://fowler-tech.blogspot.com/

Steven Fowler, Principal
Fowler Consulting
www.steven-fowler.com
fowler-tech.blogspot.com

Tirath wrote:
thanks for your reply, but i dont know how to import profile into Sharepoint
for a user created on machine only?


"madhur" wrote:

Hi

Did you check the user profiles. You might have to correctly import the
user profiles.

Madhur

Tirath wrote:
hi,
but in case of local computer accounts, "My Site" gets created, but the user
display name remains "servername\account name". How do you change this for
local computer accounts to display full name?

Thanks

"sharepointdev" wrote:

Mr. Bill:
Thanks for your reply.
I could get My Sites for domain users and local computer accounts
without any problems.

So, As I understand it: If the portal site users should have profiles,
and My Sites, then we can only use domain accounts.

Thanks,
Vamsi

Bill English, MVP wrote:
Not sure what you tried, but as long as the user has an account in AD, it
should work. I don't know if it will work using another LDAP provider and
I'm nearly entirely sure it won't work for forms authentication.

--
Bill English, MVP
Mindsharp



"sharepointdev" <motaparthyvamsi@xxxxxxxxx> wrote in message
news:1163546489.383114.297580@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Is MOSS built to have User Profiles and My Sites capability for
non-domain users, meaning users accessing the site using LDAP or SQL
based forms authentication?

MS guys: please confirm? If Yes: please provide configuration needed.

I tried many configurations to get it to work but no use. Please help.
Thanks in advance..
Vamsi






.

Relevant Pages

  • Re: MOSS My Sites for non-AD users
    ... I've successfully create a custom LDAP membership provider for use on ... importing profiles. ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Need to read "Store password in reversible encryption for all users in the domain"
    ... I always avoid the LDAP provider like the plague. ... as well as servers in domains. ... You can use these filters in ADUC. ...
    (microsoft.public.windows.server.scripting)
  • Re: LDAP Authentication
    ... What matters is the backend LDAP store you are trying to use. ... The membership provider framework is extensible, so you could write your own LDAP auth membership provider that is coded to work with Sun One. ... Co-author of "The .NET Developer's Guide to Directory Services Programming" ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: LDAP Authentication
    ... One of the things with the membership provider framework is that you don't actually have to implement every single interface member when building your provider. ... Most of the complexity stems from managing all that stuff and figuring out the LDAP details to make that work on your given directory platform. ... Co-author of "The .NET Developer's Guide to Directory Services Programming" ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: ADSI Query to filter out machine accounts in the domain
    ... Active Directory hierarchy using the Lightweight Directory Access ... LDAP is the only system-supplied Active Directory ... Service Interfaces provider that supports directory searching." ...
    (microsoft.public.dotnet.languages.csharp)