This one is a bit confusing, but I figured out what's going on. Based on how this should work, I'm guessing this is a bug or a temporary restriction until they are ready to release the full capabilities. The restriction is happening based on the logic of this script include function in the 'WalkUpUtil' script include.
/**
* Ensure that the user only has the walkup_login
* and no other roles. If user has any roles other
* than walkup_login or snc_internal, then the are not
* authorized
*
* @param user a ScopedUser
*/
isAuthorized: function(user) {
var WALKUP_LOGIN = 'sn_walkup.walkup_login';
var SNC_INTERNAL = 'snc_internal'; // used when explicit_roles plugin is active
if (!user || typeof user !== 'object')
return false;
if (!user.hasRole(WALKUP_LOGIN))
return false;
var roles = user.getRoles();
for (var i = 0; i < roles.length; i++)
if (roles[i] !== SNC_INTERNAL && roles[i] !== WALKUP_LOGIN)
return false;
return true;
},
The bottom line is that any user attempting to access the walk-up experience needs to have the 'sn_walkup.walkup_login' role (and optionally the 'snc_internal' role and NO OTHER ROLES WHATSOEVER. I created a test account with just the 'sn_walkup.walkup_login' role, logged out, logged back in, impersonated that account, and I was able to get past those error messages. Good luck!
