Re: Passing Around AuthorizationRefs
Re: Passing Around AuthorizationRefs
- Subject: Re: Passing Around AuthorizationRefs
- From: James Masasaki <email@hidden>
- Date: Thu, 23 Oct 2003 21:48:14 -0700
Yes, but that was not my question.
My question was: can two *user-level* apps do this. I understand how
an app can pass it to its helper tool and back, but can two
completely separate apps do it?
My product has one 'control-panel' app (which creates the ref and
holds it), and one "engine" app that the 1st app launches.
I need to pass the ref from the 1st app to the 2nd one.
Thanks,
James
===========================
At 9:44 PM -0700 10/23/03, Duane Murphy wrote:
--- At Thu, 23 Oct 2003 15:44:25 -0700, James Masasaki wrote:
Is it possible to pass an AuthorizationRef from one application or
process to another?
Yes, I know that security-wise it is not the best idea, but
technically is it possible and will the AuthorizationRef work in the
app that it is passed to if the sender was the app that created it?
There are times when one app wants to launch another app as part of
its architecture and the child app needs to repeatedly make access
that requires authentication, but doesn't want to continuously prompt
the user with endless authorization dialogs every time it needs to do
a privileged operation.
Is it possible to have the parent app create the AuthorizationRef,
have the child process copy it via
AuthorizationCreateFromExternalForm, and then have the child process
use it?
If you look at MoreAuthSample, this is close to what is done. In
MoreAuthSample the tool relaunches itself passing in the
AuthorizationRef. If I recall the original AuthorizationRef comes from
the main application.
...Duane
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.