IP Library Granted Patent US 12,093,428
Granted Patent B2
US 12,093,428 · App. 17/141,542 · Granted Sep 17, 2024

Restricting access to application functionality based upon working status

Inventors: Simon Brooks (Palo Alto, CA); Hemant Sahani (Palo Alto, CA); Lucas Chen (Atlanta, GA); Josh Olson (Prior Lake, MN)
Assignee: Omnissa, LLC
G06F21/629G06F21/51G06F21/54G06F2221/032G06F2221/2141
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 12,093,428
App. No.
17/141,542
Granted
Sep 17, 2024
Kind
B2
Abstract

Examples for determining access to restricted features of an application are disclosed. A current working status of a user account and an access policy can be analyzed to determine whether access to the restricted feature should be granted or denied. The functionality can be provided by a library bundled within an application.

Claims (44)

1. A system, comprising:

at least one computing device comprising at least one processor circuit; and

program instructions executable by the at least one computing device that, when executed, direct the at least one computing device to:

detect a shift status update from a time management system, the shift status update associated with a user account in the time management system;

determine a current working status associated with the user account in the time management system;

obtain a request to access at least one feature in an application executed by a client device, wherein the application determines whether to permit access to the at least one feature is based on a determination of the current working status associated with the user account that is made within a library provided by a software development kit (SDK) used to generate the application;

determine that the request is associated with the user account in the time management system, wherein the library provided by the SDK makes a network call to the time management system on behalf of the application; and

transmit the current working status to the application,

wherein the application determines to deny access to a first feature of the application based upon a determination that the current working status indicates that the user account is currently not working and to grant access to a second feature of the application based upon the determination, and the second feature is also available in the application when the current working status indicates that the user account is currently not working, and

wherein a logic to access the time management system is not bundled within the library, and the library is configured to support other time management systems provided by varying third parties with varying APIs.

2. The system of claim 1 , wherein the current working status comprises an indication of whether a user associated with the user account is currently identified as working according to the time management system.

3. The system of claim 1 , wherein the current working status comprises an indication of that the user account is designated as on-shift or off-shift.

4. The system of claim 1 , the application is instrumented to invoke a functionality of the library by one or more API calls to the library, allowing the application to request the library to make a determination of whether the application should grant an access to a restricted feature within the application.

5. A system, comprising:

a client device comprising at least one processor circuit; and

an application executable by the client device that, when executed, directs the client device to:

detect a request to access a restricted feature of the application, the restricted feature being accessible only when a user account associated with the application is indicated as on-shift;

query a policy server to retrieve an access policy associated with the user account, the access policy specifying at least one policy regarding when the user account is permitted to access the restricted feature, wherein the application queries the policy server by invoking a library provided by a software development kit (SDK) used to generate the application;

retrieve a current working status associated with the user account from a time management system, wherein the library provided by the SDK makes a network call to the time management system on behalf of the application;

determine whether the user account is permitted to access the restricted feature based upon the current working status and the access policy;

cause access to the restricted feature to be blocked in response to determining that the user account is not permitted to access the restricted feature based upon the current working status and the access policy; and

grant access to another feature in response to determining that the user account is not permitted to access the restricted feature based upon the current working status and the access policy,

wherein a second feature is also available in the application when the current working status indicates that the user account is currently not working, and

wherein a logic to access the time management system is not bundled within the library, and the library is configured to support other time management systems provided by varying third parties with varying APIs.

6. The system of claim 5 , wherein the application is instrumented to invoke a functionality of the library by one or more API calls to the library, allowing the application to request the library to make a determination of whether the application should grant an access to a restricted feature within the client application.

7. The system of claim 6 , wherein the application further comprises a user interface overlay that blocks visibility of the restricted feature, wherein the application further blocks user input to the restricted feature.

8. The system of claim 5 , wherein the application determines to permit access to the restricted feature to be blocked when the current working status indicates that the user account is off shift.

9. The system of claim 5 , wherein the application determines to cause access to the restricted feature to be blocked by determining that a location of the client device is outside a geographic boundary specified by the access policy.

10. The system of claim 5 , wherein the application determines to cause access to the restricted feature to be unblocked in response to determining that current working status indicates that the user account is on shift.

11. The system of claim 5 , wherein the application detects the request to access the restricted feature of the application by detecting an inbound notification to the application, and the application causes the restricted feature to be blocked by suppressing the notification until the current working status indicates that the user account is on shift.

12. The system of claim 5 , wherein the application detects the request to access the restricted feature of the application on startup of the application, and the application causes the restricted feature to be blocked by causing the application to exit.

13. A method, comprising:

detecting a request to access a restricted feature of an application, the restricted feature being accessible only when a user account associated with the application is indicated as on-shift;

querying a policy server to retrieve an access policy associated with the user account, the access policy specifying at least one policy regarding when the user account is permitted to access the restricted feature by invoking a library provided by a software development kit (SDK) used to generate the application;

retrieving a current working status associated with the user account from a time management system, wherein the library provided by the SDK makes a network call to the time management system on behalf of the application;

determining whether the user account is permitted to access the restricted feature based upon the current working status and the access policy;

causing access to the restricted feature to be blocked in response to determining that the user account is not permitted to access the restricted feature based upon the current working status and the access policy; and

granting access to another feature in response to determining that the user account is not permitted to access the restricted feature based upon the current working status and the access policy,

wherein a second feature is also available in the application when the current working status indicates that the user account is currently not working, and

wherein a logic to access the time management system is not bundled within the library, and the library is configured to support other time management systems provided by varying third parties with varying APIs.

14. The method of claim 13 , wherein the application is instrumented to invoke a functionality of the library by one or more API calls to the library, allowing the application to request the library to make a determination of whether the application should grant an access to a restricted feature within the application.

15. The method of claim 13 , wherein determining to permit access to the restricted feature to be blocked when the current working status indicates that the user account is off shift.

16. The method of claim 13 , detecting the request to access the restricted feature of the application further comprises detecting an inbound notification to the application, and the application causes the restricted feature to be blocked by suppressing the notification until the current working status indicates that the user account is on shift.

17. The method of claim 13 , further comprising detecting the request to access the restricted feature of the application on startup of the application, and wherein causing the restricted feature to be blocked comprises causing the application to exit.

Assignments (4)
PATENT ASSIGNMENT Recorded Aug 5, 2024
From: VMWARE LLC
To: OMNISSA, LLC
Reel/Frame 068327/0365 →
SECURITY INTEREST Recorded Jul 3, 2024
From: OMNISSA, LLC
To: UBS AG, STAMFORD BRANCH
Reel/Frame 068118/0004 →
CHANGE OF NAME Recorded Apr 15, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067102/0242 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 5, 2021
From: BROOKS, SIMON; SAHANI, HEMANT; CHEN, LUCAS; OLSON, JOSH
To: VMWARE, INC.
Reel/Frame 054813/0622 →
Continuity (1)
Related Publication 20220215106A1 · Jul 7, 2022