PersonService

[daviesd <da...@oclc.org>]

What is the right way to create a Person if your shindig implementation is
abstracted away from your authentication model?

For example, we have a website that authenticates and sets some
cookie/session information.  We cannot plug into the authentication flow in
order for it to create an entry into our database that will support the
PersonService.  The only thing we can do is the first time a request is made
that needs a Person record, we can create that record using the limited
amount of data we have in our token.  However the first request may not be
to the PersonService at all, but possibly to UserPrefs.  We don¹t want to
plug in to each service.  Ideas?

Doug