-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
.NET user won't authorize #3674
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Bump |
What keys did you set on parse-server? did you provide a dotNetKey? |
Use use the "clientKey" for OSX, "restAPIKey" for RESTful, and the "dotNetKey" for the .Net app. (The example above I just put in placeholders - but in real life ;P ... I Copy/Paste the correct keys into the app directly from the Index.JS file setup for that parse server instance) I assume the "WindowsKey" in the configuration parameter that is supposed to be filled in with the dotNetKey from the server instance. |
Bump |
Can someone post a "Startup" project for VB or c# that works with pointing to your own parse server? |
Well - something just started working. |
Damn you beat me to it!!!!! You need to add "/" at the end. In the sdk all calls append the remaning url to the server url. |
I swear - I swear I tried that before. BUT.... here we are here today. It's all working now. |
Hahaha yas!!!! |
Issue Description
I am able to authorize a user via REST and OSX just fine. But I am building VB.NET application (VS2015) to no avail.
I am greeted "Invalid response from server"
Steps to reproduce
If I add a "/" to the end of the server address I get an "unauthorized" message back.
Expected Results
CurrentUser to be set
Actual Outcome
ex.Message = "Invalid response from server" after the LogInAsync is called
Environment Setup
Server
Database
Logs/Trace
Include all relevant logs. You can turn on additional logging by configuring VERBOSE=1 in your environment.
Cleaned out logs, ran .NET program again. no logs
Again - it works fine via REST and OSX (using same ApplicationID and server - albeit different client keys of course).
The text was updated successfully, but these errors were encountered: