External User Registration Application – Some Screenshots And Details

Thank you everyone for the great feedback and interest in our external users registration app.  I had hoped that people would find it useful and I think we have a way of distributing it at no cost to anyone interested.

The app is a single Domino database which has two versions depending on whether you want users to be able to register themselves or be invited to register by your internal users.  I’ve tried to show both below

The Notes menu is very simple because it’s not intended to be used by anyone other than the occasional administrator.  Everything else is done via a web interface

The Notes client menu

The Notes client menu

First you need to set up the configuration telling the app where the Directory that will contain external user names is.  This the directory that TDI will reference when creating policies but user accounts aren’t copied into it until the registration process is entirely complete.

This setup is for the internal registration app

Setup

This is the registration page for the public registration where anyone can sign up for access. Obviously you could modify this to have further checks in place but bear in mind Connections only allows access for external users to Communities they are invited into so if I did register myself and login, I wouldn’t be able to see or do anything without a further invite.

We ask for an email address and confirm the registration back to that address asking the external user to click a link to activate – that way we ensure the email addresses are valid and monitored.  The code also checks that no one else has registered with the address already

RegistrationPublic

An external user would then receive an email with an activation link to click on

ConfirmationEmail

The registration page used for the internal invite model is slightly different but still checks the email address being registered is not already being used.

RegisterInternal

Then generates a unique registration code that can be emailed out to the external user manually (or automated if you want to add that code)

RegisterInternalConfirm

In each case the activation screen resulting from clicking on the link is the same. The password requirements can be modified by changing the code.

Activation And finally when the external user creates a valid password they get the following screen

Confirmation

So how do you get hold of a version of the app?  Obviously this is only part of the external user registration process which also includes LDAP and TDI configuration.  I would be very happy to quote on helping you with those pieces too but it’s not a requirement you use my consultancy to get access to the app, we are happy to make it available. I believe the setup can be completed in 2 – 3 hrs at most and again I’m happy to bill you to do that if you need me to or you can ask another Business Partner. You are welcome to take the app and support it yourself but in all cases our copyright remains in place (and is everywhere 🙂

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Please email Mike Smith (mikes @ turtlepartnership.com) or myself if you need more information or a copy of either the public registration or internal registration app. Bear with us and we’ll get it out to you as soon as we can.

Domino 9.0.1 FP4 Crashes With HTTP On Linux and AIX

I discovered this on a customer site this weekend.  Their servers are running SLES Linux 64bit and already had Domino 9.0.1 FP2 on them.  I upgraded to  FP4 but only one of the clustered mail servers runs iNotes – that server kept crashing as soon as someone tried to access their mail.  The other server was stable and if I disabled HTTP the crashing server stayed up.

Turns out the IBM installer for FP4 on Linux and AIX is setting the ownership of the dojo folder incorrectly which causes the crash.  The dojo folder is under <notesdatadirectory>/domino/js and the ownership was set to invalid names.  From the js directory (which just has the dojo folder in it) I ran

chown notes:notes * -R

which told Linux to change the ownership of the dojo folder and everything beneath to the account / group used to run Domino.

There is a technote dated 28th August that i’ll post here but the fix on the technote is incorrect.  On their fix they say the permissions are wrong and need changing to 755 using chmod but that’s not true, they are already 755 in my installs but the actual ownership is wrong.  Maybe they’ll fix the technote but the background is here http://www-01.ibm.com/support/docview.wss?uid=swg21964549