JakeRattner1
6 years agoQrew Cadet
API Security
Hi All,
I'm working with a development team and want to limit their access to sensitive data within our application. The developer will require making extensive API calls. I'm aware that this level of access can be used to gain access to basically all parts of an application.
The proposed work around is to create a duplicate application, without sensitive data, where they can conduct most of their work prior to going live. The developer would be provided API access to this new application only. Is this possible?
I've read the documentation here: https://help.quickbase.com/api-guide/authentication_and_secure_access.html.
It appears to indicate that if the user is authenticating through a 'User Token' this can be made app specific and the develop will not be able to access other applications within the domain. If the developer is authenticating through a 'Ticket' then that ticket can be used to access the entire domain. Therefore, the developer should be given access only to the duplicate application and should authenticate through a 'User Token' they create. Is this correct?
If anyone has experience with this I would love any feedback you can offer.
Thanks!
Jake
------------------------------
Jake R
------------------------------
I'm working with a development team and want to limit their access to sensitive data within our application. The developer will require making extensive API calls. I'm aware that this level of access can be used to gain access to basically all parts of an application.
The proposed work around is to create a duplicate application, without sensitive data, where they can conduct most of their work prior to going live. The developer would be provided API access to this new application only. Is this possible?
I've read the documentation here: https://help.quickbase.com/api-guide/authentication_and_secure_access.html.
It appears to indicate that if the user is authenticating through a 'User Token' this can be made app specific and the develop will not be able to access other applications within the domain. If the developer is authenticating through a 'Ticket' then that ticket can be used to access the entire domain. Therefore, the developer should be given access only to the duplicate application and should authenticate through a 'User Token' they create. Is this correct?
If anyone has experience with this I would love any feedback you can offer.
Thanks!
Jake
------------------------------
Jake R
------------------------------