Appeal 2007-0732
Application 09/799,502
in FIG. 2, a client application 210 is coupled with a gateway 220, which is
coupled with a user profile database 270 and first, second, and third server
applications 230, 240, 250 in a host environment 260." (Id. ll. 23-26.)
"[T]he gateway 220 can incorporate security functionality. End users
of the gateway 220 can be authorized to access one or more services through
the use of user security profiles maintained in the user profile database 270."
(Col. 4, ll. 42-46.) According to this functionality, "security needs only be
managed once (upon logging into the gateway 220). . . ." (Id. ll. 61-62.)
"For a web-based client, [the Secure Sockets Layer protocol] can be used to
encrypt input user-id and password." (Id. ll. 51-52.)
In other words, a user submits his user-id and password to the
gateway 220. The gateway compares the submission against stored sets of
user-ids and passwords to determine whether the user is authorized to access
any of server applications 230, 240, and 250. To enable the comparison, we
find that a skilled artisan would know that the reference's system must store
sets of user-ids and passwords in some storage unit. The sets may be stored
in the user profile database 270, which "can be a part of or separate from the
gateway 220" (id. ll. 47-48), or in some other storage unit of the system.
IV. USING LOG-IN DATA
The Examiner makes the following additional findings.
[A]ccording to Navarre, "once authentication is complete, the
user profile is used to create a menu of the services accessible
by the client for that session" (Navarre, co1.4, lines 53-55).
7
Page: Previous 1 2 3 4 5 6 7 8 9 10 Next
Last modified: September 9, 2013