- Learning Azure Functions
- Jenkins Continuous Integration Cookbook
- Jenkins Essentials – Second Edition
- DevOps for Web Development
- Implementing DevOps with Microsoft Azure
- DevOps Bootcamp
- Jenkins Essentials
In wake of the latest iOS cloud breach, it has become crucial to secure your Google Drive account to avoid unauthorized access. The following article highlights essential tips to help you maximize the security of your Google drive.
Almost everyone is aware of the latest iOS cloud breach, where anonymous hackers have managed to hack a number of celebrity accounts and leaked their explicit pictures. It is a very unfortunate that there will always be someone attempting to gain unauthorized access – somewhere and at someplace. This is why, it is important you secure your Google Drive account as soon as possible.
Since you’re most likely to connect to your Drive via your smartphone or tablet, therefore it will be useful to follow some simple tips to keep your account safe:
- Share With Care
Sharing files and folders is very convenient with Google Drive. But, this feature can lead to an insecure account. It is important you keep a few essential things in mind while sharing any file on Google Drive. Firstly, only share your files and folders with people you can completely rely upon. Avoid sharing documents blindly. Secondly, always share as view-only files, unless a specific user needs editing access.
- Employee Encryption
There are numerous apps that work in conjunction with cloud accounts and function to encrypt all your data transmissions. Boxcryptor is one such widely used app. This is an Android app that allows the user to encrypt all files and folders within the Google Drive Account, such that only the user can view those files. In addition, you can also encrypt the files on your Android device before they are synchronized with your Google Drive accounts. They can be encrypted using RSA-4096 and AES-256 standard. You can trust the security offered by this service.
- Check App Permissions
While working on your Android device, most often you grant permissions to a variety of services and apps. There are times when you even give off permissions to such apps and services that request to view your Google Drive account information. So, before granting permissions, make sure you always keep this in check and do not leave any pending permissions for apps and devices no longer in use. Leaving any permissions hanging can hamper your Google Drive Security.
- Wireless Security
Never use your Google Drive Account when you are using an unsecured wireless network. In case you find yourself on an unsecured network and you wish to use your Google Drive, the best option for you is to turn off the Wi-Fi setting on your device and use your carrier’s 3G network. After all, you’ll be better off trusting the security of your mobile data than an unsecured Wi-Fi network. This is also true for online shopping, online banking or while using any service where account sensitive service would be transmitted.
Download Eclipse IDE for Java EE Developers from http://www.eclipse.org/downloads/
Install Google Plug-in for Eclipse and follow instructions given at: http://code.google.com/eclipse/docs/install-eclipse-3.6.html
Google Plug-in for Eclipse
Figure 1 – GAE Plugin Installation in Eclipse
Next -> Review Items to be installed
Next -> Review Licenses – Select the radio button – I accept the terms of License Agreement – Click Finish
It will take some time to install GAE environment in your local system.
Click New-> Select Google -> Select Web Application Project
Figure 2 – Google Web Application Project
Deselect Google Web Toolkit from Google SDKs Section
Figure 3 – Google SDK settings for Web Application
Figure 4 – Web Application Structure for GAE
It is a normal web application structure and the only difference is appengine-web.xml
Table 1 – appengine-web.xml Structure
|<?xml version=“1.0” encoding=“utf-8”?><appengine-web-app xmlns=“http://appengine.google.com/ns/1.0”><application></application><version>1</version><!–
Allows App Engine to send multiple requests to one instance in parallel:
<!– Configure java.util.logging –>
<property name=“java.util.logging.config.file” value=“WEB-INF/logging.properties”/>
HTTP Sessions are disabled by default. To enable HTTP sessions specify:
It’s possible to reduce request latency by configuring your application to
asynchronously write HTTP session data to the datastore:
<async-session-persistence enabled=”true” />
With this feature enabled, there is a very small chance your app will see
stale session data. For details, see
Now just open http://localhost:8888 in browser
Figure 5- Local Environment of GAE
Click on GAETest to run it in local environment
Figure 6 – Execution of GAE Application in Local Environment
Deploy Sample Hello, Open Source For You web application on GAE
Figure 7 – Deploy Application to GAE from Eclipse
To deploy it on GAE, Authentication is required.
Provide username and Password in a new window.
Accept the terms of service and privacy policies.
If Application ID is not set then Deployment process will give error: “GAETest does not have an application ID”
To create an application Id -> Open https://appengine.google.com Login and Create New Application ID
Figure 8 – Create Application Identifier for GAE Application
Click on Create Application. It will give message “Application Registered Successfully” if all goes well.
To proceed further, Click on the project settings link in the same dialog box.
Figure 9 – Provide Application Identifier in Eclipse Properties
Click ok and Application ID error will be solved. Now Click on Deploy.
Figure 10 – Deploy Project to GAE
Once the deployment Process will complete, Console output will be like:
Table 2 – Deployment Output from Eclipse
|———— Deploying frontend ————|
Preparing to deploy:
Created staging directory at: ‘C:UsersadminAppDataLocalTempappcfg1977774409461224969.tmp’
Scanning for jsp files.
Scanning files on local disk.
Cloning 2 static files.
Cloning 23 application files.
Uploading 3 files.
Uploaded 1 files.
Uploaded 2 files.
Uploaded 3 files.
Sending batch containing 3 file(s) totaling 4KB.
Deploying new version.
Closing update: new version is ready to start serving.
Uploading index definitions.
Deployment completed successfully
Now let’s verify the GAE dashboard and verify the status of newly deployed application:
Figure 11- Application Status in GAE Dashboard
Let’s run the application:
Figure 12 – Available Servlets for an App in GAE
Figure 13 – Web Application in GAE Environment