401 response from PostIterationToWardenPanelAsync

[lincmii]

I receive a 401 response from PostIterationToWardenPanelAsync in my Warden Console Service when POSTing to localhost:11223. Using fiddler and postman, I reconstructed the POST and sent via postman. Following this, I received the valid 204 and my mongodb updated accordingly.

The WardenPanel is hosted via IIS 7.5 and was pulled from Warden.Web.Warden.Web, and Warden Console Service from Warden.Examples.Console.

[spetz]

While using the following code:

.IntegrateWithHttpApi("https://localhost:11223/api",
    "my-api-key",
    "my-organization-id")   

are you certain that both api key and organization id are valid and the user with selected api key has access to the organization? Also, would that possible for you to set the breakpoint in the ApiController to see if the api key validation works properly?

[lincmii]

After further debugging I've narrowed the problem not to the code but to
the way I've configured IIS to host the app. The 401 error I was receiving
had to do with the IIS failing to authenticate NTLM. I apologize, this was
my first time using a dotnet core application. I've resolved the 401 error
by configuring the app pool as No Framework and Integrated. Thank you.

On Oct 7, 2016 8:55 PM, "Piotr Gankiewicz" notifications@github.com wrote:

While using the following code:

.IntegrateWithHttpApi("https://localhost:11223/api",
"my-api-key",
"my-organization-id")

are you certain that both api key and organization id are valid and the
user with selected api key has access to the organization? Also, would that
possible for you to set the breakpoint in the ApiController to see if
the api key validation works properly?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#131 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABb4iy74AkBP9GFvLMFgZrywawWqjc4Aks5qxz5tgaJpZM4KRidN
.

[spetz]

That's good to hear that everything works fine and don't apologize, I'm here to provide the answers for any questions :). This web app is no longer being developed, though, as we're working on the new API and Web App with much better UI & UX, so stay tuned.