• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Authorization Services Username/Password?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Authorization Services Username/Password?

  • Subject: Authorization Services Username/Password?
  • From: "Huyler, Christopher M" <email@hidden>
  • Date: Fri, 31 Oct 2003 16:41:33 -0500
  • Thread-topic: Authorization Services Username/Password?
If I already know the username and password of the user, can I use
Authorization Services to test their validity without popping up a
dialog?

I noticed there are a few constants for the name tag of an
AuthorizationItem in the doc: kAuthorizationEnvironmentUsername and
kAuthorizationEnvironmentPassword. Can I use these to specify a
username and password to send when calling AuthorizationCopyRights?

We currently use crypt() and since that will no longer work with
"Panther" I am seeking alternative solutions. We only need to know if
the person entered a correct username/password for the computer they are
connecting to. I would also like to know if the user is an
"administrator" of the computer if possible. The username/password is
obtained from a java gui which can be launched remotely from a web
browser on any platform. It sends the information to a daemon which
does the check and returns success or failure.

--
Christopher Huyler
Computer Associates Intl.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
  • Prev by Date: RE: Freelance programming
  • Next by Date: Sending objects using sockets and NSFileHandles I'm working with some sockets and file handles for the first time, and I want to send an image across a network, would this be an appropriate way to do it (conceptually): 1. Client sends string message "image" to server (using writeData:) 2. Server receives string data "image", and so sends image as data (using writeData:) 3. Client now receives image data and converts it to an NSImage. Is this the appropriate way to send images and other objects? Or is there a more conventional method.
  • Previous by thread: Getting updated documentation
  • Next by thread: Sending objects using sockets and NSFileHandles I'm working with some sockets and file handles for the first time, and I want to send an image across a network, would this be an appropriate way to do it (conceptually): 1. Client sends string message "image" to server (using writeData:) 2. Server receives string data "image", and so sends image as data (using writeData:) 3. Client now receives image data and converts it to an NSImage. Is this the appropriate way to send images and other objects? Or is there a more conventional method.
  • Index(es):
    • Date
    • Thread