I created new project in BIM360 using BIM360 user account. (say account1)
Snapshot 1
Then activated BIM360 Field Service.
Snapshot 2
Then I shared that Project with other BIM360 user account. (Say Account2)
Now I'm trying to access that shared project using Account2 in BIM360. I was able to access the Project in BIM360 DOCS Also I was able to create new Daily Update in it though BIM360 DOCS-> Field Management.
But the shared project isn't visible in Account2's BIM360 FIELD UI.
I was trying to create new daily in shared project using Account2 credentials with help of daily_updates API. But I wasn't able to access that shared project in Projects API using Account2.
Is it the expected behavior?
Or did I miss something while sharing project?
Related
When permission is given to user via publish app, it doesn't apply read permissio to the dataset if the dataset resides in another workspace.
Example: Say dataset is in WorkspaceA. Report connecting to this dataset is in WorkspaceB. I create an app in workspaceB- in app permission tab I add user who can access the app.
This doesn't automatically give read permission to the dataset since it resides in a different workspace. I have to manually give read access to users via the 'manage permissions' on the dataset.
Also, the checkmarks like the Allow all users to connect to apps underlying dataset using build permission, allow users to make copy of reports, allow users to share app and apps underlying dataset using share permissions seem to have no effect. What is the reason for this?
I'm building a system to manage documents using Django, so I want to allow specific users (based on their ID o email) to read specific documents (uploaded by the same user or shared with another one specified by the file creator).
How can I build this feature?
Just resolved by using Google Buckets: every user has a bucket on Google Storage and the database in django webapp stores relationship user/bucket/credentials for access.
Google API Admin SDK Data Transfer: Can be found here
I have been able to successfully copy over all files from 1 Google account to another, but I am looking to copy over just 1 specific file. Scopes and permissions are correct.
The successful API request body to move all files is:
{
"oldOwnerUserId": "{ID transferring from}",
"newOwnerUserId": "{ID Transferring to}",
"applicationDataTransfers": [
{
"applicationId": "{Google Drive Application ID}"
}
]
}
The ID for the Google Drive Folder I'm looking to copy over is 1HCrNywrvoUly_MrYndR. How can I adapt this code to only transfer over this Google Drive folder?
Alternatively, is there a way I can create default folders in other user's accounts through the Google API? I need to create a set of blank folders for every new user that creates an account and haven't been able to find a way to create folders in other accounts using the Google Drive API. This workaround is to create all folders in my Google Drive and then using the Admin SDK API to ship off the completed folder to the new user.
After digging around, I found a solution that was way less complicated than using a Google Service Account. All you need is Admin credentials.
if you create a folder in your own Google Drive through the API, you can load it up with whatever you want. After that, you can then change the permissions of the parent folder to make the target user an owner. You then delete your own permissions and voila, that file now belongs to the other person.
Answer:
The Admin SDK API does not have methods which allow you to copy a single file or folder from one user account's Drive to another. For this, you must use the Google Drive API.
More Information:
You will need to use a service account to do this, as to authorise an application as more than one user you must have an application being run with an account that has domain-wide delegation, but once this has been set up in your Google Cloud Project Console, you can use the regular Google Drive API methods to copy individual files or folders from one Drive to another.
Things to be aware of:
You will need to use the delete and add methods of the Drive API to create the files/folders, rather than copying them.
If there are files inside a folder you wish to copy over, you will need to copy these recursively into the newly created folder.
You can get a list of the files in a folder using the list method of Drive: files in the API.
References:
Google Cloud - Understanding service accounts
Google Drive API
Method Files: create
Method Files: delete
Method Files: list
I'm developing new features for this open source application, but i don't know how to create the APK for where i upload it to the store. does anyone have any idea on how to do this? i'm new to all of this so i appreciate the help.
this is the link for the source code https://github.com/guh/berrylan
I already tried looking on the documentation of Qml to see which one they used to developed this app
If it is an open source application, you probably don't want to be uploading it to the store yourself, especially if you haven't discussed the process with the project leads.
there can be only one application with the same package name / Application id for most app stores
if you change the package name / application id it is incredibly confusing for users to know which app to use
this means most App stores will block the app as a "copycat"
even if the project is open source, if you want to replace the original app in the app store you need the signing key. Putting this signing key is a huge security mistake. If you did this then malware authors could compile a version of the app with "new features" that hurt the user or cost them money, getting the app banned. As a result most open source project don't keep the key in the project, and you'd need to contact the original uploader
even if you had the key, For Google you'd need access to the Play store developer accounts. Which would mean having your gmail address added as trusted for the account owner. Which means you'd need to contact the project owner
In summary, even if an app is open source, publishing to a store is a big step which needs contact with the project owners if you don't want to get you or the app banned.
We're using Google Analytics API in our application and perform actions (read data) on behalf of our users (we get their tokens via OAuth2). We use a client id and client secret to authorize our Google API project (application).
The problem is that we're unable to reach this project in Google's developer console, because the user in our Google App account who created this project was deleted. Regardless, the Google API still works (we have the key and the client secret) but we're unable to reach it in the admin section in the browser, but we can't access it because the owner was deleted.
What are the options to recover access to this API project? Is it possible to transfer ownership of this project using Google API? It's running in production so we can't afford to generate a new API project.
Is it perhaps possible to generate a new API project by keeping all our users consents (they authorize their accounts using an authorization popup in our web app)?
EDIT: it's also possible the user still exists, but we don't know who's the owner. Is it possible to retrieve this info using the app's api key/secret?
How to find out who owns your credentials.
Authenticate your application the pop up window will appear. Click on the name of the application the little arrow and a drop down will apear with the email address of the developer who owns the project.
If you have lost access to this account i am not aware of any way of getting access back. However for the sake of curiosity i am going to contact someone at Google and find out if they have a procedure for account recovery or not. I will update this when i hear back.
If the account that has a credential was a gsuite user then we can transfer the project to the admin of the domain.
Have the admin of the GSuite contact me with information on the project, client id, email of the user who was deleted. We can then add the admin of the gSuite as the owner of the project.
From the question, this was likely a gsuite user because even after the account is deleted, the project was not deleted.