Staging Authorization
I'm developing a C# application to access our community and am having difficulty authorizing with the Staging environment for testing. Is it possible to automatically provide the username / password...
Forum Discussion
It sounds like you've got the right process as far as basic authentication is concerned. Here's an example that another community user had from their Java source code, for comparison:
URL categoryUrl = newURL("http://forums.mycompany.com/.../restapi/vc/categories/nested");
BASE64Encoder encoder = new BASE64Encoder();
String encodedCredential = encoder.encode( (userId + ":" + password).getBytes() );
httpUrlConnection.setRequestProperty("Authorization", "BASIC " + encodedCredential);
The first thing I'd suggest is checking to make sure you have the right URL for the call. What happens when you attempt to access the URL in your browser? Do you see a successful response? If your IP address isn't whitelisted, you may need to enter the basic authentication credentials in your browser as well.
When I try to access the same URL from a browser I receive our root list of Categories, so I don't think there's a problem with the URL. The response comes after the login prompt from the staging server which means my IP address hasn't been whitelisted.
Is automatic login (or more accurately automatically validating the tester's requests) in the C# application possible? I don't want to require our test team to log in since that behavior isn't consistent with the production server.
Thanks for any help you can offer!
It is possible to add IP addresses or IP address ranges to the whitelist for your staging environment so that requests from those IP addresses will not require the basic authentication. It sounds like that might be the easiest path for you at this point. In order to get that setup, I'd suggest submitting a request via our Customer Case Portal (the "Support" tab up above). Our support team should be able to assist with adding the necessary IP addresses to the whitelist. You will need to provide them with the externally-facing IP address that the requests will be coming from.
Thanks again for your help. I figured out the problem: it was my lack of knowledge of how Basic Authorization works. I was expecting to send the authorization information in my first HTTP request and receive a 200 response. What I overlooked is the first response from the server must be 401. After that, I can supply the authorization info in my HTTP header and the server will authorize my client.
