Forum Activity for @brian

brian
@brian
12/05/17 09:27:20AM
10,149 posts

User api key


Proxima

Any access to Proxima requires an API key. So if you have 10 different remote applications (they can be mobile, other servers, etc) then you would need to have 10 different API keys.

There is no "open" API access to Jamroom using Proxima.
brian
@brian
12/05/17 09:11:14AM
10,149 posts

User api key


Proxima

So what you want to do here is just create a new app key manually for the few customers you want to give access to your site via the Proxima API. This lets you vet who is getting access to your site as well.

Let me know if that helps.
brian
@brian
12/04/17 03:14:32PM
10,149 posts

User api key


Proxima

I'm not 100% sure what you mean in regards to:

Quote:
I need users from one of my quotas to be able to connect directly through api

I just want to be sure what you are looking to do. Your users can connect via Proxima to your site - that's not an issue. You could restrict those connecting to a specific quota if you wanted to as well.

The part I am not understanding is why you need different "apps". Are the users in this quota going to be building their own mobile apps that need to connect with your site in some way?

Quote:
Jamroom is not designed to handle multiple users accessing through the api.

You could have thousands of different users connecting to your site using Proxima - that's not an issue. They would all connect using the same APP key and a unique session key - so that's not an issue.

Let me know if that helps at all.

Thanks!
brian
@brian
12/04/17 01:08:23PM
10,149 posts

User api key


Proxima

Proxima is not designed for users to create apps - i.e. it's not an "app platform". It's designed for solo app developers who need a backend and website to sell their apps from - i.e. they create the apps and the users are users IN their apps.

I know that's probably not what you're looking for, so want to be sure you know what Proxima was designed for.
brian
@brian
12/04/17 12:38:07PM
10,149 posts

User api key


Proxima

DannyA:
1. Not a big deal, but never seen one shorter than 32 characters. And I want app developers to feel secure.

The API keys used in Proxima can contain 16^57 different values, so they're no chance of collision. The API key is not secret, so it's not a security issue.

Quote:
2. To generate their own keys. The apps will be dependent on their quota. I don't want to have to manually create keys for every user. Was hoping they could generate a key from their account settings.

I think there's some confusion here, or you're using Proxima in a way it was not intended. Your users will not create Proxima API keys - YOU create them for your app, and your users registers session in the app. There is no API interface for creating apps.
brian
@brian
12/04/17 12:15:55PM
10,149 posts

User api key


Proxima

DannyA:
No, in both cases I referring to the proxima application keys.
/api/app_browser

Got it. What's the reason they need to be longer? Right now they are hard coded at 16 characters.
brian
@brian
12/04/17 11:55:24AM
10,149 posts

backup worker doesnt finish working


Installation and Configuration

Do you see the backup files ending up in S3? is mysqldump executable by the web user? Not really sure what else to recommend. Your server seems to have issues with running binaries under the web server.
brian
@brian
12/04/17 11:54:23AM
10,149 posts

User api key


Proxima

DannyA:
1. is there any way to increase the default length of the keys generated?

I'm guessing you mean the user session key? If so no - it's an MD5 hash.

Quote:
2. How can I let a user generate keys associated with his account/quota?

I'm not sure what you mean here - do you mean session keys? They will generate a new one each time they log in.

Let me know if that helps.
brian
@brian
12/01/17 09:29:42AM
10,149 posts

Unable to Install Marketplace Items


Installation and Configuration

Welcome to Jamroom!

This error means that Jamroom is unable to rename a directory to a symlink on your server, which is how Jamroom modules work (by switching symlinks to the active module). We've seen this on some hosting providers - basically they don't allow the web user to create/delete/rename symlinks. I'd contact your hosting provider and make sure symlinking is allowed in your hosting account.

Let me know if that helps.

Thanks!
brian
@brian
11/30/17 08:34:47AM
10,149 posts

Apple’s macOS High Sierra Security Flaw root access without password !


Off Topic

a bad bug for sure, but also reinforces the idea that without physical security you can't have system security.
  94