We are happy to say that this often requested subject is going to happen -- the current target date is November 8, 2012. After single sign-on is put in place, Be Communities members will go through a one-time account consolidation process, where you will be prompted for your Be Communities sign-in name and then your Bentley Web username to "match" them. You will need to select a new 6-8 character password, making it so you will use one sign-in to get to any Bentley Web property (e.g. www.Bentley.com, SELECTservices Online, Bentley LEARN Server, AND Be Communities). We will not change your member account information, so your "screen name" on Be Communities will continue to be what it is now.
Should you have any questions, please feel free to ask so we can help make this process as simple as it is intended to be.
We came across a few issues, so this will not be put in place on November 8. However, we are working to address what was found and move forward with this as soon as possible. When we determine a new date for implementation, we will provide that information here.
We continue to progress on addressing issues found during testing of the single sign-on consolidation. Our next target for putting this in place is December 6, 2012. Since the text used in the user interface is still being changed (to make for a good user experience), we are not quite ready to provide "documentation" on it. We are looking to make that available about a week ahead of the consolidation process going live.
This was mentioned in the initial post in this thread, but since that was a while ago, after single sign-on is put in place and you successfully go through the consolidation process, you will use one sign-in to get to Bentley Web properties (e.g. www.Bentley.com, SELECTservices Online, Bentley LEARN Server, AND Be Communities).
We are looking at Thursday, December 13 to put the Be Communities consolidation in place. Information regarding this is accessible online at http://www.bentley.com/en-US/Services/consolidate+be+communities+login.htm. As mentioned previously, should there be any questions, please feel free to ask.
As it is now 13/12/12 how do we start this consolidation process as I've just signed in as normal. The link you gave is just information and is not live.
The Web page referenced is informational... it identifies the "workflow" when the consolidation process is put in effect. The latter should start towards end-of-business today (US Eastern time).
OK. So that's nearly 14/12/12 for us in the UK!
I think that I am using the same password for all sites but I've no idea of knowing as IE has remembered my password. I didn't go througn the consolidation process as shown in the informational page.
Can someone one let me know whether it is my BE communities or my SELECTservices password I'm using.
During the consolidation process, you need to use both. The first thing you are asked for is your Be Communities credentials. If that succeeds, then you are asked for your "other Bentley Web property" credentials. Then you are asked for a new password for your "other Bentley Web property" credentials. If that succeeds, you will then have one set of credentials that will get you in to Be Communities, SELECTservices Online, Bentley LEARN Server, etc. It is just that easy and is all explained fairly well on www.bentley.com/.../consolidate+be+communities+login.htm.
If there is one thing I DON'T want it is to mix my activity and emails from BeC with correspondance with Support.
regards / Thomas Voghera
Let's put the conspiracy theories to rest, okay? :)
Seriously, what this thread communicates is that we are consolidating the SIGN-ON for Be Communities to be the same as our other Web properties. That way, if you want to go to SELECTservices Online, Be Communities, Bentley LEARN Server, etc. you only have to sign-on using one set of credentials. And when you change that, it changes in one place (and not two, or more places).
That said, we do have a long range goal where information transfer is more streamlined, since the "social" aspect is part of Support. But, more on that later (and in parallel discussions, so as to no hijack this thread).