Forums

Brad Turner

I made the change but no change in the amount of error detail I get back.  BTW, this is MOSS 2007.

 Hmm... I'll look into this and see if I can't recreate.Which site def are you targetting?

Brad Turner

QUESTION: When the account is auto-created, can it be used to sign direclty in with or is it just for passthrough purposes?  What is it storing as the password - the password hash from AD?

for now it's for passthrough. Password is a custom password that is then emailed back to the user who is prompted to change it. In AD-AD set ups (or possibly Forms - Forms) then it wouldn't make a difference as the same account would work in both.

Brad Turner

FYI: I had to be added to Site Collection Administrators in order to see the Global Settings page.  Is there any documentation on what the activity list selection does?  I see every list on the site displayed but I'm not sure I understand how this works.  I added one, but not sure what it's doing...

well, I've discovered a bug in that system so it's possible you're not seeing anything right now because of that. But, the feature essentially will update the new Activity Message stream in Community Server with actions that take place in lists that have opted-in to notify the message stream.

So, in Document Libraries, if you check a doc out, the stream will be updated "Leon has checked out 'doca' from shared documents" with links to SharePoint.

FYI - if I get the CS URL "wrong", either because of the host header not being present, or by forcing the url to HTTPS, it crashes the page the CS web parts are on. 

I'll test HTTPS again once my host header issues are worked out!

[EDIT] This did indeed work once I got the host header registered in DNS properly.  However, setting the communityserver.config ssl="All" crashed the web part page.  I can configure the CS URL to use HTTPS now, but setting the site to require SSL crashed the REST API interaction somehow.

lgersing

Hmm... I'll look into this and see if I can't recreate.Which site def are you targetting?

Targeting the root site collection "/", but I'm adding the webparts to a sub-site within the same site collection.

lgersing

for now it's for passthrough. Password is a custom password that is then emailed back to the user who is prompted to change it. In AD-AD set ups (or possibly Forms - Forms) then it wouldn't make a difference as the same account would work in both.

Ok, that might explain some of it, it appears that loading the page with the webpart on it is the action that triggers account creation (COOL!) and I'm guess something got "hosed up" when we were trying to get the webparts loaded before.  I deleted the accounts in CS and reloaded the page - now at least I see the forums filtered by by Role and not all forums like before.  I also didn't have email configured on the CS site so I never got the email that my account had been created.  I configured SMTP, but still no email - it might be hung up in our spam filters; however.  Getting closer, but still no page yet...

QUESTION: How do the enrollment settings correspond to the ability for the REST API to auto-enroll users?  I had it set to require approval and that was overriden.

SUGGESTION: It would be helpful to have the ability to add a filter to the webpart to only display certain forums, for example.  Auto-filtering by Roles is way powerful, but I can see some value in adding a filter at the webpart level as well to focus content on specific pages if required.

lgersing

the basics of the asumptions.. is that if a user exists in SharePoint with AD then we look for that user in CS. If they don't exist we create the user with information from SharePoint and notify the user of their new account. There are several bits of information we look at, not just username, to try and autodiscover this.

Unfortunately, it looks as if there is still a bug in that match and when it happens you get the "you do not have access" error from the REST service.

So, the default setup with CS using Forms Authentication is ok as it's checking AD under the hood for the SharePoint user?

 Any ideas on how I can troubleshoot this bug?

I confirmed that the auto-notification is not working.  I tried the following configuration:

• Allow Login: Yes
• Allow New User Registration: Yes

I changed the Account Activation to both Email and Admin Approval and while the account gets created automatically after loading the webpart, it never emails the user their password.

lgersing

Hmm... I'll look into this and see if I can't recreate.Which site def are you targetting?

Ok, I think I've narrowed this down to one error condition - the CommunityServer Global Site Definition Extensions feature failed to activate.  If I try to activate the feature then I get the following error:

Value does not fall within the expected range

I believe this may be related to the single failure I have during installation:

Value does not fall within the expected range.

stsadm.exe -o activatefeature
...
Feature 'CSGlobalExtensionStapler' (ID: 31e82773-2938-4141-9c3a-813900f3fd33) is already activated at scope 'Farm'.

I tried to create a new Team Site and I get the same "Value does not fall with the expected range" error as well so I'm betting it's all tied to same feature.  While in this condition I can get the Site Activity Messages webpart to work as well as the Forum Groups webpart, but clicking on anything results in the 404 I described earlier in the thread.

I tried a full uninstall and reinstall and I the same failure message.

HELP!  We're so close!

Do anyone have a detail instruction on Configuring SharePoint (MOSS) Integration for Community server 2008?

From Configuring SharePoint Integration for Community server 2008 procedure

1. Open your browser and navigate to the home page of the Root level SiteCollection to which you installed SharePoint. You should see a message stating, "Please configure Community Server". This means that the features were installed successfully but are not configured.

Is this about Community server 2007?

Thank you for any ideas?

. Open your browser and navigate to the home page of the Root level SiteCollection to which you installed SharePoint. You should see a message stating, "Please configure Community Server". This means that the features were installed successfully but are not configured.

Is this about MOSS(SharePoint 2007)?

The version you're working with is significantly different than the final product.

If you have an immediate need, please contact me at cvanderbeck@telligent.com and we can discuss.

If you can hold out, we're going to be releasing the RTM in the next days!

I'll be posting a Q&A doc tomorrow that will answer many questions about the product and integration points.

Thanks for your interest!

Christian

The matching is problematic in that it doesn't appear to recognize [domain\user] as the same as [user] causing me some headaches by creating a new user for me after setting myself as admin on install. Smart software often isn't for reasons just like this. A couple of suggestions for future releases:

1. Take domain into account when matching

2. Prompt users when multiple names/other criteria match. It's better to annoy me once with a question than continually by auto-logging me in as the wrong person.

3. Genrally speaking it seems like the setup should be concerned with more AD-related questions. What groups, what users, which domains in the forest, etc.

lgersing

Yeah, that's an obstaclue for us as well in the design (Forms vs AD). But the basics of the asumptions (as they stand today and are, btw, subject to change) is that if a user exists in SharePoint with AD then we look for that user in CS. If they don't exist we create the user with information from SharePoint and notify the user of their new account. There are several bits of information we look at, not just username, to try and autodiscover this.

Unfortunately, it looks as if there is still a bug in that match and when it happens you get the "you do not have access" error from the REST service.

Hi Brad,

I got the same error.

Feature 'CSGlobalExtensionStapler' (ID: 31e82773-2938-4141-9c3a-813900f3fd33) is already activated at scope 'Farm'.

Were you able to resolve this?

Thanks.

There were some issues with urls in early releases, make sure you have the most recent release to resolve a few issues.  Let me know if you have any trouble.

Thanks,

Brendon

Yeah everything is fixed in the recent releases.