T
Tejas Ranade
Guest
Sometimes, your data sources may reside on infrastructure that’s not directly exposed to the internet, which can result in all sorts of challenges. Kinvey’s Secure Gateway makes connecting to these data sources much easier.
Kinvey Services enable developers to connect to external data and auth systems. For example, one could create a service to connect to a Microsoft SQL Server database, authenticate against ADFS or implement a piece of logic that orchestrates data from three different REST endpoints. As a part of our mobile microservices framework, the Kinvey platform comes with the RapidServices feature—no-code, configuration-based modules that enable you to connect to a variety of popular external systems.
A big challenge that many of our customers face in adopting RapidServices is that their data sources reside on infrastructure that’s not directly exposed to the internet. As a result, they cannot connect to these data sources from their Kinvey backend. Making such systems available to their apps involves cumbersome security reviews, firewall configuration changes, VPN setup, etc. In some cases, this may not be an option at all.
With Kinvey’s Secure Gateway, we aim to make this process much easier for our customers. The Secure Gateway includes a client tool that you can install inside your firewall. You can then have the gateway client open a bidirectional, secure channel with a gateway server running on Kinvey. You can then setup RapidServices to transfer data through this secure channel.
How It Works
Let’s say your app needs to connect to a SharePoint server sitting inside your company firewall. The SharePoint host name is myHost.myService.com and it is running on port 3000.
To begin, you install the Secure Gateway client inside your network:
$ npm install -g Kinvey/secure-gateway-client
From the secure client, you create a new connection:
$ kinvey-secure-gateway-client create <name>
This above command will return a connection ID. You use this ID to start a connection that will establish a tunnel from the gateway server to your SharePoint server:
$ kinvey-secure-gateway-client start <connection-id> myhost.myservice.com 3000
When the connection is started, the gateway server will return a server port number to the client (for example, 6767). From now on, any request to/from gateway.kinvey.com:6767 will be forwarded to myhost.myservice.com:1234. Create a RapidService with the host as https://gateway.kinvey.com:6767, and you have securely established a connection to your SharePoint server!
Kinvey Secure Gateway is currently available for trial. We’d love to have developers try it and share their experience with us. If you’re interested in getting access to Kinvey Secure Gateway, get in touch!
Continue reading...
Kinvey Services enable developers to connect to external data and auth systems. For example, one could create a service to connect to a Microsoft SQL Server database, authenticate against ADFS or implement a piece of logic that orchestrates data from three different REST endpoints. As a part of our mobile microservices framework, the Kinvey platform comes with the RapidServices feature—no-code, configuration-based modules that enable you to connect to a variety of popular external systems.
A big challenge that many of our customers face in adopting RapidServices is that their data sources reside on infrastructure that’s not directly exposed to the internet. As a result, they cannot connect to these data sources from their Kinvey backend. Making such systems available to their apps involves cumbersome security reviews, firewall configuration changes, VPN setup, etc. In some cases, this may not be an option at all.
With Kinvey’s Secure Gateway, we aim to make this process much easier for our customers. The Secure Gateway includes a client tool that you can install inside your firewall. You can then have the gateway client open a bidirectional, secure channel with a gateway server running on Kinvey. You can then setup RapidServices to transfer data through this secure channel.
How It Works
Let’s say your app needs to connect to a SharePoint server sitting inside your company firewall. The SharePoint host name is myHost.myService.com and it is running on port 3000.
To begin, you install the Secure Gateway client inside your network:
$ npm install -g Kinvey/secure-gateway-client
From the secure client, you create a new connection:
$ kinvey-secure-gateway-client create <name>
This above command will return a connection ID. You use this ID to start a connection that will establish a tunnel from the gateway server to your SharePoint server:
$ kinvey-secure-gateway-client start <connection-id> myhost.myservice.com 3000
When the connection is started, the gateway server will return a server port number to the client (for example, 6767). From now on, any request to/from gateway.kinvey.com:6767 will be forwarded to myhost.myservice.com:1234. Create a RapidService with the host as https://gateway.kinvey.com:6767, and you have securely established a connection to your SharePoint server!
Kinvey Secure Gateway is currently available for trial. We’d love to have developers try it and share their experience with us. If you’re interested in getting access to Kinvey Secure Gateway, get in touch!
Continue reading...