IP Library Granted Patent US 10,530,812
Granted Patent B2
US 10,530,812 · App. 15/086,495 · Granted Jan 7, 2020

Methods and apparatuses for providing configurable security models

Inventors: Yana Poliashenko (Alpharetta, GA); Latonia M. Howard (Stone Mountain, GA)
Assignee: HYLAND SOFTWARE, INC.
H04L63/20H04L63/08H04L63/10
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,530,812
App. No.
15/086,495
Granted
Jan 7, 2020
Kind
B2
Abstract

A method, apparatus and computer program product provide an application server implementing configurable security models. An example of the method includes receiving a first access request from a first client application, determining a first client identifier for the first client application based at least in part on the first access request, using the first client identifier to identify one or more first security models associated with the first client application from a database, the database comprising a plurality of client identifiers and a plurality of indications of security models associated with each of the plurality of client identifiers, executing an application instance providing functionality in accordance with the one or more first security models, and processing the first access request using the application instance.

Claims (50)

1. A method executed by a processor of an apparatus for implementing an application server supporting configurable security models, the method comprising:

receiving a first access request from a first client application executing on a first client device;

determining a first client identifier for the first client application based at least in part on the first access request;

identifying a first security model associated with the first client application from a database using the first client identifier, the database comprising a plurality of client identifiers and a plurality of indications of security models, each of the security models associated with at least one of the plurality of client identifiers in the database, wherein the first client identifier is associated with the first security model due to the first client application being updated with an update, wherein a second client identifier of a second client application executing on a second client device is associated with a second security model in the database due to the second application failing to be updated with the update;

executing a first application instance providing functionality to the first client application in accordance with the first security model due to the first client application being updated with the update;

processing the first access request using the first application instance;

receiving a second access request from the second client application executing on the second client device;

determining the second client identifier for the second client application based at least in art on the second access request;

identifying the second security model associated with the second client application from the database using the second client identifier, the second security model being different from the first security model;

executing a second application instance providing functionality to the second client application in accordance with the second security model due to the second client application failing to be updated with the update; and

processing the second access request using the second application instance.

2. The method of claim 1 , further comprising determining one or more parameters associated with the first security model, wherein the first application instance further implements the one or more parameters.

3. The method of claim 2 , wherein the one or more parameters are further associated with the first client application.

4. The method of claim 2 , wherein the one or more parameters define at least one of a public key, a private key, a hash salt value, or an order of authentication processes.

5. The method of claim 1 , wherein the second application instance providing functionality in accordance with the second security model is different from the first application instance providing functionality in accordance with the first security model.

6. The method of claim 1 , wherein the second client application implements a previous version of a security model implemented by the first client application.

7. The method of claim 1 , wherein each of the security models define at least one of an encryption algorithm, an availability of a single sign-on operation, or a hash value.

8. The method of claim 1 , wherein the first client application and the second client application are electronic health records applications.

9. An apparatus for implementing an application server supporting configurable security models, the apparatus comprising a processor and a memory, the memory storing instructions that, when executed by the processor, configure the apparatus to:

receive a first access request from a first client application executing on a first client device;

determine a first client identifier for the first client application based at least in part on the first access request;

identify a first security model associated with the first client application from a database using the first client identifier, the database comprising a plurality of client identifiers and a plurality of indications of security models, each of the security models associated with at least one of the plurality of client identifiers in the database, wherein the first client identifier is associated with the first security model due to the first client application being updated with an update, wherein a second client identifier of a second client application executing on a second client device is associated with a second security model in the database due to the second application failing to be updated with the update;

execute a first application instance providing functionality to the first client application in accordance with the first security model rather than the second security model due to the first client application being updated with the update;

process the first access request using the first application instance;

receive a second access request from the second client application executing on the second client computing device;

determine the second client identifier for the second client application based at least in part on the second access request;

identify the second security model associated with the second client application from the database using the second client identifier, the second security model being different from the first security model;

execute a second application instance providing functionality to the second client application in accordance with the second security model due to the second client application failing to be updated with the update; and

process the second access request using the second application instance.

10. The apparatus of claim 9 , the processor further configuring the apparatus to determine one or more parameters associated with the first security model, wherein the first application instance further implements the one or more parameters.

11. The apparatus of claim 10 , wherein the one or more parameters are further associated with the first client application.

12. The apparatus of claim 10 , wherein the one or more parameters define at least one of a public key, a private key, a hash salt value, or an order of authentication processes.

13. The apparatus of claim 9 , wherein the second application instance providing functionality in accordance with the second security model is different from the first application instance providing functionality in accordance with the first security model.

14. The apparatus of claim 9 , wherein the second client application implements a previous version of a security model implemented by the first client application.

15. The apparatus of claim 9 , wherein each of the security models define at least one of an encryption algorithm, an availability of a single sign-on operation, or a hash value.

16. The apparatus of claim 9 , wherein the first client application and the second client application are electronic health records applications.

17. A non-transitory computer readable storage medium comprising instructions that, when executed on a processor of an apparatus, cause the processor to implement a system for providing configurable security models, the instructions configuring the processor to:

receive a first access request from a first client application executing on a first client device;

determine a first client identifier for the first client application based at least in part on the first access request;

identify a first security model associated with the first client application from a database using the first client identifier, the database comprising a plurality of client identifiers and a plurality of indications of security models, each of the security models associated with at least one of the plurality of client identifiers in the database, wherein the first client identifier is associated with the first security model due to the first client application being updated with an update, wherein a second client identifier of a second client application executing on a second client device is associated with a second security model in the database due to the second client application failing to be updated with the update;

execute a first application instance providing functionality in accordance with the first security model due to the first client application being updated with the update;

process the first access request using the first application instance;

receive a second access request from the second client application executing on the second client computing device;

determine the second client identifier for the second client application based at least in part on the second access request;

identify the second security model associated with the second client application from the database using the second client identifier, the second security model being different from the first security model;

execute a second application instance providing functionality to the second client application in accordance with the second security model due to the second client application failing to be updated with the update; and

process the second access request using the second application instance.

18. The computer readable storage medium of claim 17 , the instructions further configuring the processor to determine one or more parameters associated with the first security model, wherein the first application instance further implements the one or more parameters.

19. The computer readable storage medium of claim 18 , wherein the one or more parameters are further associated with the first client application.

20. The computer readable storage medium of claim 17 , wherein the first client application and the second client application are electronic health records applications.

Assignments (17)
RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 045870/0395 Recorded Sep 24, 2023
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
To: HYLAND SOFTWARE, INC.
Reel/Frame 065018/0046 →
RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 045870/0389 Recorded Sep 24, 2023
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
To: HYLAND SOFTWARE, INC.
Reel/Frame 065019/0704 →
SECURITY INTEREST Recorded Sep 19, 2023
From: HYLAND SOFTWARE, INC.
To: GOLUB CAPITAL MARKETS LLC, AS COLLATERAL AGENT
Reel/Frame 064952/0333 →
RELEASE AND REASSIGNMENT OF CERTAIN PATENTS RECORDED AT R/F 044096/0852 Recorded Aug 30, 2023
From: JPMORGAN CHASE BANK, N.A.
To: ALLSCRIPTS SOFTWARE, LLC
Reel/Frame 064761/0037 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT SUPPLEMENT (SECOND LIEN) Recorded Apr 9, 2018
From: HYLAND SOFTWARE, INC.
To: CREDIT SUISSE
Reel/Frame 045870/0389 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT SUPPLEMENT (FIRST LIEN) Recorded Apr 9, 2018
From: HYLAND SOFTWARE, INC.
To: CREDIT SUISSE
Reel/Frame 045870/0395 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 9, 2018
From: ALLSCRIPTS SOFTWARE, LLC
To: HYLAND SOFTWARE, INC.
Reel/Frame 045480/0747 →
SECURITY INTEREST Recorded Nov 10, 2017
From: ALLSCRIPTS SOFTWARE, LLC
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 044096/0852 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 19, 2017
From: MCKESSON CORPORATION
To: PF2 MCKESSON TECHNOLOGIES INC.
Reel/Frame 043904/0271 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 19, 2017
From: PF2 MCKESSON TECHNOLOGIES INC.
To: PF2 EIS LLC
Reel/Frame 043904/0405 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 9, 2017
From: ALLSCRIPTS HEALTHCARE US, LP
To: ALLSCRIPTS SOFTWARE, LLC
Reel/Frame 043815/0967 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 9, 2017
From: PF2 EIS LLC
To: ALLSCRIPTS HEALTHCARE, LLC
Reel/Frame 043815/0918 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 9, 2017
From: ALLSCRIPTS HEALTHCARE, LLC
To: ALLSCRIPTS HEALTHCARE US, LP
Reel/Frame 043815/0939 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 12, 2017
From: MCKESSON FINANCIAL HOLDINGS UNLIMITED COMPANY
To: MCKESSON CORPORATION
Reel/Frame 041355/0408 →
CHANGE OF NAME Recorded Jan 11, 2017
From: MCKESSON FINANCIAL HOLDINGS
To: MCKESSON FINANCIAL HOLDINGS UNLIMITED COMPANY
Reel/Frame 041329/0879 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 31, 2016
From: MCKESSON CORPORATION
To: MCKESSON FINANCIAL HOLDINGS
Reel/Frame 039887/0935 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 31, 2016
From: POLIASHENKO, YANA; HOWARD, LATONIA M.
To: MCKESSON CORPORATION
Reel/Frame 038156/0152 →