Skip to content
This repository has been archived by the owner on Jan 18, 2022. It is now read-only.

retrieving access token from keychain #2

Closed
GoogleCodeExporter opened this issue Aug 11, 2015 · 3 comments
Closed

retrieving access token from keychain #2

GoogleCodeExporter opened this issue Aug 11, 2015 · 3 comments
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

What steps will reproduce the problem?
1.trying to access the token from keychain


What is the expected output? What do you see instead?
i want to set the token directly and perform the upload. Instead a pop up comes 
asking the permission to access the keychain.

What version of the product are you using? On what operating system?
GTM-OAUTH2 in  Mac OS X 10.6


Please provide any additional information below.
i neednot require any pop ups that asks permission which allows or denies it. i 
want the upload to be done directly

Original issue reported on code.google.com by u.krishn...@gmail.com on 5 Oct 2011 at 5:33
@GoogleCodeExporter
Copy link
Author 

This is normal behavior for Mac OS X. Secure storage of user authorization 
tokens in the keychain will raise a permission dialog for the app the first 
time the app accesses the keychain.

Original comment by grobb...@google.com on 5 Oct 2011 at 7:01

@GoogleCodeExporter
Copy link
Author 

ok. if i want the access token to be stored somewhere other than keychain.and  
to access it when i upload a video. is this possible

Original comment by u.krishn...@gmail.com on 7 Oct 2011 at 6:25

@GoogleCodeExporter
Copy link
Author 

While the authentication class has persistenceResponseString methods that allow 
getting and setting the authentication value as a string, the keychain is the 
only secure storage provided by Mac OS X, so we strongly encourage developers 
to use the keychain rather than other, less-secure mechanisms.

Original comment by grobb...@google.com on 7 Oct 2011 at 9:17

@fornaxM fornaxM mentioned this issue Apr 28, 2016
Closed
@sera8705 sera8705 mentioned this issue Jul 19, 2019
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@thomasvl @GoogleCodeExporter