We have recently deployed a basic web based solution which allows each user to manage the documents they have created in a basic web dashboard.
Now the company is moving towards obtaining various ISO certification and it is now a requirement to add an authentification mechanism in front of the dashboard.
Users are required to login with their Microsoft Active Directory account before they can now view and manage their documents.
I know the Workflow NodeJS Server preference has a setting for allowing users to login before the process is run. This presents the user with a basic and default web interface which the company doesn’t want to use as it doesn’t meet the company ‘s look and feel.
The company has provided their own fully styled html snippet for the login page. The snippet works really well in a Connect template but we have issues integrating it with the NodeJS authentification mechanism of Workflow.
We have spent 3 days so far and are nowhere near being able to send the user login details to AD using their custom personalised and styled login page. Managing user sessions become a real challenge.
Does OL have a guide one can follow to integrate a login page designed in Connect work with a company’s Active Directory LDAP?
The default login.ejs and login-successful.ejs files served by the NodeJS Server input are located in C:\Program Files (x86)\Objectif Lune\ppnode\src\html.
You can replace them (after backing them up, of course!) with your own HTML code, you simply have to make minor adjustments to integrate the <%=user%>, <%=msg%> and <%=temp%> variables that the NodeJS Server automatically passes to the login.ejs template.
Take a look at the original files, you should be able to quickly figure where each variable goes inside the HTML file generated by Connect.
I have looked into this and somehow managed to edit the ejs and css files. I must admit I had never worked with EJS before, so it’s a good learning curve. The issue is that the login page and mechanism do not behave as expected:
1- I don’t see how and where to control the login page url. The company wants a url that they would recognise, but the url that is presented to the user seems to be set somewhere in one of your scripts. Could you please advise on how to edit the url ?
2- If the user successfully logs in and then clicks on the Back button of the browser, then we get a random web page which says the user is already logged in. Could you point out where this other page comes from? Ideally, at that point the user should be redirected to the original login page.
Now, I have heard OL support mentioning using WordPress in front of my processes to control login through AD but at the same time they don’t seem to know how this is setup nor are they able to advise on the above two questions.
I would be grateful if there was a clear step by step guide explaining how this is done either through Wordpress that OL seems to now champion or through the inbuilt nodejs server available in the Workflow. I have been at it for weeks…please help.
Please simplify this process in future releases and bring in features or plugins which allow AD, Azure and Auth2 authentication mechanism. These features are now a must have for most clients we have spoken with.
At the moment this is far too complex to setup for a normal user. We have still not managed to set this up correctly in Connect.
Unfortunately in this case, the prospect has moved to the competitor.