Custom login screen for Appian Cloud

garym over 8 years ago

Hi,
Has anyone on a cloud implementation put in a "front-end" login screen instead of using the Appian login screen.
With the current login screen, it is assumed that the user has a username and password already.
However, what if we want a new user to be able to go to our site, fill in a form to create a login (just like someone signing up for an amazon account) and then have that login created in our Appian user database.
It would be nice to have the standard functionality such as the setup of a security question (what is your pet's name) and a check to see if the current login exists. Also, the check to see if it is a robot trying to create an account. These are standard items that you see on most websites where a login is required.
I'm assuming this has to be done via some third-party "front end" and if anyone has done something like this already, can you please share your experiences and what technologies were involved.

Thanks,
Gary

Discussion posts and replies are publicly visible

Parents

0 Sidhant Behura over 8 years ago

@garym - You can create a registration form in html and get it hosted.Then you can create a process model which takes in all the inputs fetched from the registration form and publish it as a web service. Then on click of submission of the registration form you can trigger this process model and use the following shared components.

Captcha - https://forum.appian.com/suite/tempo/records/item/lMBCLGOdlMUpdGVqW3dQaIKmclBmvvNEj8vu_cjb7T-5YiPr4Fu8ly5Yj1s09uenE4RYzA8zKyx7eiUh-mvLnNz7pWaADqvf87Q9fmzA6MWEu8g7g/view/summary
Personalization Utilities(creating users specifying the i18n preferences and it verifies whether an username is available to create a new account) - https://forum.appian.com/suite/tempo/records/item/lIBCLGOdlMUpdGVqW3dQaIKmclBmvvNEj8vu_cjb7T-5YiPr4Fu8ly5Yj1s09uenE4RYzA8zKyx7eiUhetE6R7wweiOH6ioZIxyCYszpaPoTE8_/view/summary
For checking whether the username already exists you can write a web api which checks whether the username exists or not (using isusernametaken()) and will return the response accordingly.
Check shared components for other.

And if you are on 16.2 then you can create Web API(s) and call OOTB smart service functions instead of creating process models and publishing it.
Of course both their own advantages which you can choose according to your requirements.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Sidhant Behura over 8 years ago

@garym - You can create a registration form in html and get it hosted.Then you can create a process model which takes in all the inputs fetched from the registration form and publish it as a web service. Then on click of submission of the registration form you can trigger this process model and use the following shared components.

Captcha - https://forum.appian.com/suite/tempo/records/item/lMBCLGOdlMUpdGVqW3dQaIKmclBmvvNEj8vu_cjb7T-5YiPr4Fu8ly5Yj1s09uenE4RYzA8zKyx7eiUh-mvLnNz7pWaADqvf87Q9fmzA6MWEu8g7g/view/summary
Personalization Utilities(creating users specifying the i18n preferences and it verifies whether an username is available to create a new account) - https://forum.appian.com/suite/tempo/records/item/lIBCLGOdlMUpdGVqW3dQaIKmclBmvvNEj8vu_cjb7T-5YiPr4Fu8ly5Yj1s09uenE4RYzA8zKyx7eiUhetE6R7wweiOH6ioZIxyCYszpaPoTE8_/view/summary
For checking whether the username already exists you can write a web api which checks whether the username exists or not (using isusernametaken()) and will return the response accordingly.
Check shared components for other.

And if you are on 16.2 then you can create Web API(s) and call OOTB smart service functions instead of creating process models and publishing it.
Of course both their own advantages which you can choose according to your requirements.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data