Not sure I understand. How are you creating issues?
I presume using the service manager, what credentials are you supplying to the constructor?

Hello Mark,

I will be following up for Diego on this issue.

We have recently upgraded from using:

Gemini Web Application: v3.5.4 (Build 2435) WebService DLLs: v3.6.4 (Build 2630)

TO:

Gemini Web Application: v3.7.0 (Build 2711) WebService DLLs: v3.7.0 (Build 2711)

This was installed on a different (new) server and the database was copied over.

Permissions are as follows: NETWORK SERVICE - All Allow (Less Full Control) Local Admin Group - All Allow Everyone - All Allow Internet Guest Account (account used for Anon access) - Read & Execute, List Folder Contents, and Read Allow Local Power Users - All Allow (Less Full Control) System - All Allow Terminal Server User - All Allow (less Full control) Local Users - Read & Execute, List Folder Contents, and Read Allow

We have run into some interesting issues that we would like some help on.

1) Some users are able to make web service calls without issue when enable anonymous access is turned off, however when it is turned on those users recieve 403 Forbidden errors, and a Gemini Rest Exception "Method Requires Auth.." 2) Regardless of what is passed into the Constructor of the ServiceManager the WS will work for 2 of the computers. Examples:
a) If we pass the correct Gemini URL, with empty strings and false to windows auth and attempt to create a ticket, one will be created with the reporter as Anon.. b) If we pass the correct Gemini URL, with only a Username filled and False for windows auth, a ticket will be created with the reporter as the username passed in. c) If we pass the correct Gemini URL, with empty strings and Windows Auth set to True, a ticket will be created with reporter as Anon.. 3) A user is able to create an issue from one PC on the domain, but cannot create an Issues from another computer on the same domain.

Are you using windows authentication in Gemini (web.config)?
It seems to me that you are and therefore, Gemini authenticates the blank user call becuase it can authenticated the calling user (who owns the process).
The problem you are having on some machines is due to the fact that anonymous access is allowed in IIS for the Gemini site. You should turn it off if you are using windows authentication.

Ok Anon access is turned off (was only turned on because that is how we got it to work with the older version)

We are using Windows Auth on the Website, but still having the same issues, detailed in the examples with number 2. Is it expected that all but the Username that is passed into the constructor of the Service manager is apparently ignored?

In windows authentication mode yes, it will always use the windows identity to authenticate and permissions.

By disabling Anon access as you suggested and setting the Boolean UseWindowsAuth = true, the issue is resolved.

Thanks for your help!