Skip to main content

The Nintex teams have been at it this last couple of months working hard on some great new initiatives influenced heavily by the requirements of our current user base, and feedback from the InspireX conference that was held in February just past.

 

Firstly, let us quickly chat about FBA support. This new capability will allow customers already using or planning to use FBA to log into SharePoint from Nintex Mobile. The latest version of Nintex Forms (2013 and 2010) is required (2.9.1.0 / 1.11.1.0), and after a small configuration change in Central Admin you will be off and running. Apple iOS and Android will be supported initially this month with Windows Desktop and Phone rolling out in the next release.

 

There are 2 sections inside Manage FBA Mobile Access.

  1. Enable Form Based Authentication for Nintex Mobile: Users can enable/disable Nintex Mobile access to Nintex Forms inside SharePoint environment using Form Based Authentication. By default, it will be disable.
  2. Set Nintex Mobile Token Expiry: When users login to SharePoint environment using Nintex Mobile, user will be issued with Token. This token will allow user to access Nintex Forms using Nintex Mobile. Users can set Token expiry in this section. Available options are 30, 60, 90 days. Default value is 60 days.
 

Note that the SharePoint farm will have to be already setup for Forms Based Authentication before Nintex Mobile FBA will work.

182942_pastedImage_5.png

 

Nintex Mobile for FBA doesn't support FBA users for a SharePoint mixed mode environment. E.g. if an organization has a SharePoint environment supporting both Windows Authentication and Form Based Authentication, Nintex Mobile will only support Windows users.

 

Note: If your network infrastructure uses a firewall, ensure that FBA endpoints are externally accessible by Nintex Mobile. FBA endpoints are located at the following URL: <SiteUrl>/_vti_bin/NintexMobile/FBA/

Secondly, in this months roll out is that Nintex Mobile will now also start to introduce Profiles. These changes will be rolled out over 2 releases for the respective platforms, starting with iOS and Android.

 

We will see some UI changes and the ability to build a profile within the app. Accompanying the profile you'll be able to associated a PIN number as well, for an even easier login experience.

 

login.jpgSelect Account.png

 

 

In the next release Nintex Mobile will allow multiple profiles on a device and multiple environments to be added to those profiles. So for those of you who are running a hybrid farm this will allow you to show both on-prem forms and O365 in the one sitting and for the shared device workers, the ability to be able to go into your profile and have saved / draft forms and easier access. This will be especially handy for us designers as well, where we want to have dev and test in your profile without having to log out and go back in to production..

 

profile.jpgScreenshot_2016-04-05-08-46-20.png

 

But like I mentioned this will be in the next release as the second part of the profile feature, which I will write more about then.

 

Wrapping up, if Forms Based Authentication has been a blocker hopefully now you can unleash Nintex Mobile and Nintex Mobile Enterprise on your organisation.. If you do I'd love to hear about it in the comments.. Profiles once fully rolled out will allow easier logins for multi user devices, and much easier for multi environment deployments.

 

For further instructions on how to setup your profile and pin see the online help files here: Signing in to the Nintex Mobile App

For more information on Nintex Mobile app profiles, see the Nintex Mobile help.

 

Until next time, have fun.

Nice one! Profiles will be really nifty for managing all my internal, demo and client testing environments...

I'm really interested to check out profiles – thanks for sharing!

The part where you say "The latest version of Nintex Forms (2013 and 2010) is required (3.1.8.0 / 2.4.8.0), and after a small configuration change in Central Admin you will be off and running." The latest version of forms I see available is "2.9.1.0" those versions you mention look to be Nintex Workflow versions. Is Nintex Workflow required to be updated as well to get the Nintex Forms functionality?

Yup you got me   .  you only need the new forms version (I'll update the post) . But it always pays to have the latest wf version as well   

In this warning, "Nintex Mobile for FBA doesn't support FBA users for a SharePoint mixed mode environment. E.g. if an organization has a SharePoint environment supporting both Windows Authentication and Form Based Authentication, Nintex Mobile will only support Windows users.". Are you able to use a trusted identity provider and windows authentication provider at the same time? Or would the same warning apply in that scenario also?

In your post you say "In the next release Nintex Mobile will allow multiple profiles." Is this feature now completely in production? My app has asked me for a pin, but I haven't figured out how to make the different user profiles available to choose from at log-in.

Thanks

Kassie

Multiple account profiles have been available on version 4.1 for Android & iOS and 4.2 on both Windows platforms. You'll be asked to provide a PIN after the first account you have added to your profile.  From there we take you straight into the app without promoting you to add any more accounts.  

If you want to add another account you'll find that you are able to do so in Settings.  In fact you can control all kinds of things in Settings such as the colour assigned to each account and whether the account is active or not.  You can even delete an account should you no longer need it.   

In short, no, you cannot use a trusted identity provider and windows authentication provider at the same time within the a single profile.

With a Multiple Account profile you are able to sign into up to 5 accounts.  These can be any combination of:

  • SharePoint on-prem (all supported versions)
  • O365
  • Nintex Workflow Cloud    

However for the Windows option we restrict it to only one account which basically means that Windows is mutually exclusive of the three other account types. This is because a Windows account can be used to aggregate a number of other SharePoint accounts together so it already serves the purpose of the Multiple Account profile.  Further to this problems would arise if your SharePoint account was being accessed by both a Windows account and directly.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings