User Setup in Alteryx Gallery as Viewer

[Dweebernot]

Hi There,

Alteryx server version 2018.1.4.

Alteryx Gallery is running on Chrome Version 72.0.3626.121 (Official Build) (32-bit)

I would like to provide a user access to a workflow. This user do not have an alteryx designer licence. This user should only have access to run the alteryx app that is created by myself. I am unable to work out how to set this up. Can you let me know what steps I should take to achieve this?

Here are the steps that I have taken:

I save my workflow to the gallery and the workflow is saved under my studio.

I add the user by clicking on Add New User, I specify the user details and check no for curator. The user is created as below

The user is created as an artisan, I believe he should be a viewer but there is no options for me to change that.

I also notice that the Permissions link is missing

[MichalM]

There different ways to achieve this @Dweebernot 

You can publish your workflow to the public portion of your Alteryx Gallery which will make it available to everyone with access to it.

Alternatively, you can add the workflow to a collection, and select users who you want to share it with.

Another way to share the workflow would be to make the user part of your Private Studio. This would however give them access to all workflows in your Studio. 

Hope that helps.

Michal

[Dweebernot]

Hi Michal,

I have tried both ways and the user can see the workflow however when he runs it, he gets the following error

Error: Logon failure: the user has not been granted the requested logon type at this computer. (1385)

I'm not sure what this error is. Does the user need to have access to the server even though we have the setting for run as set to a service account?

Appreciate any help.

Cheers

Siew Ho
Manager, Robotics & Automation
Business Intelligence & Operations
Australia Post
​
Level 20, 111 Bourke Street
​ Melbourne
​ VIC
​ 3000
​
T 0436631301
​
​E Siew.Ho@auspost.com.au
​
Australia Post is committed to providing our customers with excellent service. If we can assist you in any way please telephone 13 13 18 or visit our website.

The information contained in this email communication may be proprietary, confidential or legally professionally privileged. It is intended exclusively for the individual or entity to which it is addressed. You should only read, disclose, re-transmit, copy, distribute, act in reliance on or commercialise the information if you are authorised to do so. Australia Post does not represent, warrant or guarantee that the integrity of this email communication has been maintained nor that the communication is free of errors, virus or interference.

If you are not the addressee or intended recipient please notify us by replying direct to the sender and then destroy any electronic or paper copy of this message. Any views expressed in this email communication are taken to be those of the individual sender, except where the sender specifically attributes those views to Australia Post and is authorised to do so.

Please consider the environment before printing this email.

[MichalM]

@Dweebernot 

The error suggests a problem with the Run as configured on the server rather than the user attempting to execute it from the Gallery interface. See here for more details.

[Dweebernot]

Hi Michal,

Thank you for your response. I would like to understand more about the Run As configuration. I currently has it configured to a service account. This service account has access to the entire server. On the gallery, when I run a workflow, it will run, I cannot tell whether it is running as myself or running as per the run as configuration. However for a non licence user, it is giving me the error.

I am inclined to think that it is not running as service account but running as myself. Despite checking the settings and the Run As check box is ticked and a service account is provided.

How can I tell for certain what it is truly running as?

[MichalM]

There's a setting on the Gallery - Admin > Workflow Credentials - where you configure the desire behaviour.

• Use default credentials - this will use the Run as account configured on your server (service account in your case)
• Require user credentials - this option will prompt you to enter your Windows user name and password and these credentials will be used as Run as
• Allow users select credentials option - this will allow the users publishing the workflow choose the desired scenario 

See here for more details.

[Dweebernot · Accepted solution]

Thank you Michal for all your input. I have managed to resolve my issue. I believe it is a combination of a few things. My first issue was that the service account was not set up correctly - It was not set up as an admin to the server and it was not set up to have local access to the server. I have corrected these two active directory issues. I have tried two different workflow credentials, one being it uses a predefined credential when I save the workflow to the gallery. This method requires me to create a credential in the gallery and share it with the non licence user. The user also have to be a member to my studio. The other one is use the default credentials. This related to the Run As configuration (which in this case is my service account). The user is still a member to my studio.