Forum Activity for @nate

nate
@nate
02/04/15 04:56:38PM
917 posts

Proxima Login fail


Proxima

So it's something on my server?
nate
@nate
02/04/15 04:55:20PM
917 posts

Proxima Login fail


Proxima

When I create a user I get a match

Quote: I/GCMMain﹕ {"code":201,"text":"Created","note":"user created and session started","data":{"_id":39,"session_id":"6ee36a4827fddc202b0cdb654cc023dc","location":"http:\/\/n8flex.com\/api\/user\/39"}}

Quote: 6ee36a4827fddc202b0cdb654cc023dc
nate
@nate
02/04/15 04:39:44PM
917 posts

Proxima Login fail


Proxima

This is what's returned

Quote: I/PaymentActivity﹕ {"code":200,"text":"OK","note":"session started","data":{"session_id":"4476e810c631dece12aa398bd73f7b00"}}

This is what's in the jr_jrproximacore_session table
Quote: cd33784ce52dce710d28bc60056e657e
nate
@nate
02/04/15 02:48:07PM
917 posts

Proxima Login fail


Proxima

No changes. I never make it this far. Proxima kicks back 401 before it ever makes it too my app.

Quote: {"code":401,"text":"Unauthorized","note":"invalid user session"}
nate
@nate
02/04/15 11:27:24AM
917 posts

Proxima Login fail


Proxima

I hate to ask you to log in, but this is my last step before I add SSL and publish.
nate
@nate
02/04/15 09:22:21AM
917 posts

Proxima Login fail


Proxima

When I test I get this. There are no other modules installed other than jr modules and the module we are testing.

Quote:
I/PaymentActivity﹕ http://n8flex.com/api/user/login?id=32&password=123456
I/PaymentActivity﹕ login response is {"code":200,"text":"OK","note":"session started","data":{"session_id":"07a37a7d95d36f9342a6c2db0aa7a9a2"}}

Posting payment

Quote:
I/PaymentActivity﹕ http://n8flex.com/api/msone/checkout/tok_15SWa9EVo3ItZB1yD88GlDgS/199/4242/29
I/PaymentActivity﹕ session id to payment is 07a37a7d95d36f9342a6c2db0aa7a9a2
I/PaymentActivity﹕ {"code":401,"text":"Unauthorized","note":"invalid user session"}

httpManger

Quote: I/httpManager﹕ session id to payment is 07a37a7d95d36f9342a6c2db0aa7a9a2

public static String postData(URI uri, String session_id){
        AndroidHttpClient client = AndroidHttpClient.newInstance("AndroidAgent");
        HttpPost request = new HttpPost(uri);
        String credentials = ClientMap.PROXIMA_PASSWORD + ":" + session_id;
        String base64EncodedCredentials = Base64.encodeToString(credentials.getBytes(), Base64.NO_WRAP);
        request.addHeader("Authorization", "Basic " + base64EncodedCredentials);
        HttpResponse response;

        Log.i(TAG, "session id to payment is " + session_id);

        try {
            response = client.execute(request);
            return EntityUtils.toString(response.getEntity());
        } catch (IOException e) {
            e.printStackTrace();
            return null;
        } finally {
            client.close();
        }

    }

updated by @nate: 02/04/15 09:25:00AM
nate
@nate
02/03/15 09:18:55PM
917 posts

Proxima Login fail


Proxima

My confusion comes from when I create a new user a session is started. If I use that session everything works. It's when I create a new session by logging in that is stops working.
nate
@nate
02/02/15 11:03:04AM
917 posts

Proxima Login fail


Proxima

I'll do a fresh install and run the app from a permanent sub domain.
nate
@nate
02/02/15 09:11:58AM
917 posts

Proxima Login fail


Proxima

I just sent it.
nate
@nate
01/31/15 10:58:36PM
917 posts

Existing users.


Proxima

I see you're preventing existing users from creating a new account. It might be helpful to return the _id so we can log in. A newly installed app won't have the exiting _id.

I guess the developer can do this but currently we would have to go around proxima because there is no valid session.
updated by @nate: 01/31/15 10:59:01PM
  67