US 11,675,932 B2
Managing content authorization in a federated application system
Jeffrey Lawrence Farber, San Mateo, CA (US); Sidney Gee-Lake Shek, Sunnyvale, CA (US); Pramod Shashidhara, Mountain View, CA (US); Deepak Kulkarni, San Jose, CA (US); and Jonathan Paul Gilbert, Kiama (AU)
Assigned to ATLASSIAN PTY LTD., Sydney (AU); and ATLASSIAN US, INC., San Francisco, CA (US)
Filed by Atlassian Pty Ltd., Sydney (AU); and Atlassian Inc., San Francisco, CA (US)
Filed on Feb. 11, 2022, as Appl. No. 17/670,040.
Application 17/670,040 is a continuation of application No. 16/449,150, filed on Jun. 21, 2019, granted, now 11,263,348.
Application 16/449,150 is a continuation of application No. 16/287,957, filed on Feb. 27, 2019, granted, now 10,354,093, issued on Jul. 16, 2019.
Claims priority of provisional application 62/738,972, filed on Sep. 28, 2018.
Prior Publication US 2022/0164461 A1, May 26, 2022
Int. Cl. G06F 21/62 (2013.01); G06F 21/44 (2013.01); G06F 21/60 (2013.01); G06F 21/64 (2013.01); H04L 9/40 (2022.01)
CPC G06F 21/629 (2013.01) [G06F 21/44 (2013.01); G06F 21/604 (2013.01); G06F 21/64 (2013.01); H04L 63/0807 (2013.01); H04L 63/0892 (2013.01); G06F 2221/2141 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A computer-implemented method for managing account access to multiple software applications using an authorization server, the method comprising:
receiving, at the authorization server, a first request to grant access for a first account to a first software application of the multiple software applications;
receiving, at the authorization server, a second request to grant access for a second account to a second software application of the multiple software applications;
determining, at the authorization server, whether a data store managed by the authorization server contains first permission data for the first account associated with the first request;
determining, at the authorization server, whether the data store managed by the authorization server contains second permission data for the second account associated with the second request;
in response to determining that the data store does not store the first permission data, sending, to a first application server associated with the first software application, a third request for third permission data for the first account;
responsive to the third request, receiving, from the first application server, the third permission data;
responsive to receiving the third permission data from the first application server, storing the third permission data in the data store managed by the authorization server; and
granting, in accordance with the third permission data, access to the first software application for the first account.