Methods and apparatuses for providing improved directory services

• US 10,404,710 B2
• Filed: 03/30/2016
• Issued: 09/03/2019
• Est. Priority Date: 03/30/2016
• Status: Active Grant

• Current Assignee: Healthstream Incorporated
• Original Assignee: Change Healthcare Holdings, LLC (UnitedHealth Group Incorporated)
• Inventors: Self, Bryan, Patterson, Michael, Lee, Vincent
• Primary Examiner(s): Arani, Taghi T
• Assistant Examiner(s): Champakesanatusptodotgov, Badridot
• Application Number:
  US15/085,259
• Publication Number:
  US 20170289166A1
• Time in Patent Office: 1,252 Days
• Field of Search: 726 6
• CPC Class Codes: G06F 16/116 Details of conversion of file system types or formats
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: H04L 61/4523 using lightweight directory access protocol [LDAP]
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/01 Protocols

Abstract

A method, apparatus and computer program product are provided for implementing an improved directory services system. An example of the method includes transmitting an access request to a directory services server, the access request comprising user credentials, receiving, in response to validation of the user credentials by the directory services server, a directory services response from the directory services server, the directory services response comprising one or more fields of directory services data generated by the directory services server, translating the directory services response to generate a generic data object, wherein the generic data object comprises one or more values derived from the one or more fields of directory service data included in the directory services response, and providing the generic data object to an application.

Claims

1. A method for implementing directory services in a computer network, the method comprising:

transmitting an access request to a directory services server, the access request comprising user credentials;

receiving, in response to validation of the user credentials by the directory services server, a directory services response from the directory services server, the directory services response comprising one or more fields of directory services data generated by the directory services server;

identifying one or more values derived from the one or more fields of the directory service data included in the directory services response based on the identifiers for one or more fields of directory service data;

translating the directory services response on client side;

receiving one or more configuration files, the one or more configuration files comprising a class definition of a Plain Old Java Object, the identifiers for one or more fields of directory service data, and one or more rules for formatting the one or more fields of the directory service data for storage in the Plain Old Java Object;

wherein said translating the directory services response comprises formatting the identified one or more values for storage in the Plain Old Java Object based on the one or more rules;

generating, based at least on the class definition of the Plain Old Java Object, wherein the Plain Old Java Object comprises the one or more values derived from the one or more fields of directory service data included in the directory services response; and

providing the Plain Old Java Object to an application.

2. The method of claim 1, wherein the application also generates the access request.

3. The method of claim 1, wherein the directory services server is implemented according to the Lightweight Directory Access Protocol (LDAP) standard and wherein the directory services response is an LDAP response.

4. The method of claim 1, wherein the configuration file comprises values encoded in a Yet Another Markup Language (YAML) format.

5. The method of claim 1, further comprising storing the Plain Old Java Object in a database.

6. The method of claim 1, wherein at least one field of the directory services response is not included in the Plain Old Java Object.

16. The method of claim 1, wherein the Plain Old Java Object is generated and initialized with default values prior to translating the directory services response.

17. The method of claim 1, wherein said identifying the one or more values derived from the one or more fields of the directory services data included in the directory services response based on the identifiers for one or more fields of directory service data comprises iterating through the one or more fields of directory services data included in the directory services response to determine fields identified within the one or more configuration files.

18. The method of claim 1, wherein the one or more configuration files further comprise rules for parsing, merging, and separating one or more fields of directory service data.

19. The method of claim 1, wherein generating the Plain Old Java Object comprises populating the Plain Old Java Object with the one or more values derived from the one or more fields of directory service data included in the directory services response at runtime.

7. An apparatus for implementing directory services in a computer network, the apparatus comprising a processor coupled to a memory, wherein instructions stored within the memory configure the processor to at least:

transmit an access request to a directory services server, the access request comprising user credentials;

receive, in response to validation of the user credentials by the directory services server, a directory services response from the directory services server, the directory services response comprising one or more fields of directory services data generated by the directory services server;

identify one or more values derived from the one or more fields of the directory service data included in the directory services response based on the identifiers for the one or more fields of directory service data;

translate the directory services response on client side;

receive one or more configuration files, the one or more configuration files comprising a class definition of a Plain Old Java Object, the identifiers for one or more fields of directory service data, and one or more rules for formatting the one or more fields of the directory service data for storage in the Plain Old Java Object;

wherein said translating the directory services response comprises formatting the identified one or more values for storage in the Plain Old Java Object based on the one or more rules;

generate, based at least on the class definition of the Plain Old Java Object, wherein the Plain Old Java Object comprises the one or more values derived from the one or more fields of directory service data included in the directory services response; and

provide the Plain Old Java Object to an application.

8. The apparatus of claim 7, wherein the application also generates the access request.

9. The apparatus of claim 7, wherein the directory services server is implemented according to the Lightweight Directory Access Protocol (LDAP) standard and wherein the directory services response is an LDAP response.

10. The apparatus of claim 7, wherein the configuration file comprises values encoded in a Yet Another Markup Language (YAML) format.

11. The apparatus of claim 7, wherein the processor is further configured to store the Plain Old Java Object in a database.

12. The apparatus of claim 7, wherein at least one field of the directory services response is not included in the Plain Old Java Object.

13. A non-transitory computer readable storage medium comprising instructions that, when executed by a processor, cause the processor to implement directory services in a computer network by at least:

transmitting an access request to a directory services server, the access request comprising user credentials;

receiving, in response to validation of the user credentials by the directory services server, a directory services response from the directory services server, the directory services response comprising one or more fields of directory services data generated by the directory services server;

identifying one or more values derived from the one or more fields of the directory service data included in the directory services response based on the identifiers for one or more fields of directory service data;

translating the directory services response on client side;

receiving one or more configuration files, the one or more configuration files comprising a class definition of a Plain Old Java Object, the identifiers for one or more fields of directory service data, and one or more rules for formatting the one or more fields of the directory service data for storage in the Plain Old Java Object;

wherein said translating the directory services response comprises formatting the identified one or more values for storage in the Plain Old Java Object based on the one or more rules;

generating, based at least on the class definition of the Plain Old Java Object, wherein the Plain Old Java Object comprises the one or more values derived from the one or more fields of directory service data included in the directory services response; and

providing the Plain Old Java Object to an application.

14. The non-transitory computer readable storage medium of claim 13, wherein the application also generates the access request.

15. The non-transitory computer readable storage medium of claim 13, wherein the directory services server is implemented according to the Lightweight Directory Access Protocol (LDAP) standard and wherein the directory services response is an LDAP response.