Skip to main content
Nintex Community Menu Bar

SP2016 Forms - Allow Anonymous Access

  • January 21, 2018
  • 7 replies
  • 12 views

rhia
Nintex Partner
Forum|alt.badge.img+15

Hey folks!

We are upgrading from SP2013 to SP2016 and have one Live Form which was previously completely anonymous on the interwebs for people to access.

SP2016's External Forms settings look ... different. It's asking me to define users at domains? 

The "Allow Anonymous Access" checkbox is greyed out. 

212376_pastedImage_3.png

Thoughts?? I am bamboozled. 

Thanks,

rhia

7 replies

rhia
Nintex Partner
Forum|alt.badge.img+15
  • Author
  • Nintex Partner
  • January 21, 2018


Dan_Stoll
Nintex Employee
Forum|alt.badge.img+12
  • Nintex Employee
  • January 21, 2018

check CA to ensure it is allowed http://CA:1234/_admin/NintexForms/LiveSettings.aspx?source=/_admin/Nintex/Management.aspx

Domains are only required if you authenticating.


rhia
Nintex Partner
Forum|alt.badge.img+15
  • Author
  • Nintex Partner
  • January 21, 2018

Thanks - you mean this, right?

Can it take a while to cascade across to update the form settings, if this is the case? We did just update this today.


Dan_Stoll
Nintex Employee
Forum|alt.badge.img+12
  • Nintex Employee
  • January 22, 2018

It will probably need to wait for an app recycle or an IISreset potentially.


rhia
Nintex Partner
Forum|alt.badge.img+15
  • Author
  • Nintex Partner
  • January 22, 2018

I think that was the key, the IIS reset -- the "Allow Anonymous Access" is now checkable (WOO!) ....however... now I'm getting this lovely issue: 

212882_pastedImage_1.png

1) Form is published (republished it twice to ensure)
2) There is no expiry date on the form. 


Forum|alt.badge.img+17
  • Nintex Partner
  • April 4, 2018

Still happening?


rhia
Nintex Partner
Forum|alt.badge.img+15
  • Author
  • Nintex Partner
  • April 4, 2018

It seems to have corrected itself in the mean time, but I know that it took 2 days ++ from the initial posting (and IIS reset). Other things may have happened that I am unaware of. We found a way around it (using another form), and ended up ignoring this problem.