rClone to mount Onedrive Business - onedrive

Whenever I try to mount my onedrive on my pc, I face an issue. Right now my Org has more than 1 onedrive. (business plan 2)
and whenever I try to connect my onedrive, I get connected to other onedrive.
So when I fill the client id, secret code created by me. it shows other user drive. what is the issue?
I tried doing alot but always failed. In rClone it shows only 1 onedrive and that is other user onedrive.
Thank you

What do you mean by another OneDrive? Another user's OneDrive? A OneDrive with the same account but different contents? Are you presented with different directories to choose from once you are authenticated? If you're an admin in your org, or they haven't disabled the functionality for users to do so, go to https://aad.portal.azure.com , click on Users on the left, search for your account and click on it (don't check it) and then click on Sign-in logs on the left hand side. Just to verify that your sign-in is actually being tracked in the tenant and you are connecting to what you think you are connecting to.

Related

upload file to google drive without human interaction via SDK

I want to upload files to google drive. I'm using C# and have referred following links to get started
https://developers.google.com/drive/v3/web/quickstart/dotnet
https://developers.google.com/drive/v3/web/manage-uploads
I'm able to upload the file successfully to google drive but my main concern is I don't want to display any sort of UI/human interaction. It should be able to automatically upload the file.
Using OAuth2.0 there is a need that we have to manage and generate access/refresh token. I have no idea how these should be managed.
Isn't there any other way where the user can have access to google drive programmatically just by sharing his/her Gmail account username/password to achieve this?
Isn't there any other way where the user can have access to google drive programmatically just by sharing his/her Gmail account username/password to achieve this?
No there is not
The user needs to authorise your app one time. After that, you can save Refresh Token and use that for future unattended use.

Google Drive Android Api reset Play Services Authorization

When debugging a GDAA app, I need to re-test a "brand new account" situation. I.e. getting the dialog that asks user to allow the Drive access:
"[YourApp] would like to: View and manage Google drive files that you
have opened or created by this app"
Is there a re-set method that would get me back to ground zero?
You can reset this via the Drive "manage apps" page on the web. Disconnect the app from your drive.
Have a look at the 'Google Settings' app on your device, in the 'Connected apps' section you should be able to select and disconnect your app. At least for other kinds of permissions (e.g. contacts), allowed apps show up there.
Edit: The same can be done via the web here.

Web Server for Upload files

I have a requirement where I want HTML FTP to be accessed by AD users. When users prompted to supply their AD credentials, the IIS/FTP should mapped them directly to their folders. What I want is, an HTML "Form" page/website when its accessed from internal/external it will prompt and users will supply AD credentials. Based on the permission set on the folders users will access only their folder and will upload to their folder only. The Upload as a Browse Button which will allow them to upload specified documents to their folder only. So, When they log into their computer at work they will be able to see what has been uploaded and will be able to open that document directly.
This is actually for Part Time Lectures, currently all the shared we have on a Windows 2008 R2 and permission set based on AD.
Is this doable via HTML or any other code or FTP itself. Even third party software which will be fine too.
It might be worth taking a look at plupload - depending on your usage, you might need to pay licensing: http://www.plupload.com

Sharepoint 2012 Authentication for non-AD users

We have a sharepoint site that is used both internally and externally. Internal users are authentication via AD and there are no issues. The external users are authenticated using STS and the Portal User Table. However whenever an external user tries to open a document they have to re-enter their login credentials.
This happens everytime they open a document unless they happen to have left the application that the document is read in is left open, i.e. if they open a word document, leave it open and then open another word document then they don't get asked for credentials.
This is obviously a royal pain as we are using the site for document review, revision and collaboration. Our systems team say this is working as designed and there is nothing that can be done about it. Is there any practical way to resolve this without the external users having to specifically configure something on their own system or network?
Thanks
Jim
Here is a solution I found quite some time ago..
In Internet Explorer, click on Tools and select Manage add-ons
Highlight Toolbars and Extensions in left navigation.
Locate SharePoint OpenDocuments Class
Right-click and click the Disable button
Close and refresh browser

Link app to dropbox

I have an app with a dropbox link capability. There is a button called link. Then a safari page is opened with dropbox, and you can link the app to your account. But since I want all the users to log in with my account, I didn't want to dysplay my email and passward on the app, but by preesing link, automatically the app is linked with my account, withought showing the passward, amd withought opening the dropbox link in safari. How can I do this?
Very bad idea. Users should use their own Dropbox account, otherwise you would possibly violate Dropbox's terms of service (you're not allowed to share your credentials) and, perhaps more importantly, any user would be able to delete or corrupt all other users' data.
The only way you could make your own Dropbox account accessible in the app, other than including your email address and password, would be to include an authorized OAuth token which could easily be extracted and abused by anyone who downloads your app.