You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+32-32Lines changed: 32 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,31 +1,31 @@
1
1
## Architecture
2
2
3
-
The **Google Club Unified Access System (UAS)** employs a structured architecture to manage authentication, authorization, and identity services. The system consists of two primary services, a shared database, and client interfaces designed for both users and admins, providing a secure, cohesive experience.
3
+
The Google Club Unified Access System (UAS) employs a structured architecture to manage authentication, authorization, and identity services. The system consists of two primary services, a shared database, and client interfaces designed for both users and admins, providing a secure, cohesive experience.
4
4
5
5
### Core Services
6
6
7
7
1.**CAS (Central Authentication Service)**
8
8
9
-
-**Purpose**: CAS handles authentication, using JWT (JSON Web Token) for secure token-based authentication.
10
-
-**Features**:
11
-
-**Fast Access to Authorities**: CAS provides quick access to user authorities, ensuring low latency.
12
-
-**Cache & Authority Control**: Caches user authorities to reduce load on the database and optimize performance.
13
-
-**Technology**: Built with **Express.js** for lightweight and efficient operation.
9
+
- Purpose: CAS handles authentication, using JWT (JSON Web Token) for secure token-based authentication.
10
+
- Features:
11
+
- Fast Access to Authorities: CAS provides quick access to user authorities, ensuring low latency.
12
+
- Cache & Authority Control: Caches user authorities to reduce load on the database and optimize performance.
13
+
- Technology: Built with Express.js for lightweight and efficient operation.
14
14
15
15
2.**ICS (Identity Control Service)**
16
16
17
-
-**Purpose**: ICS focuses on managing identity and access control for both users and administrators.
18
-
-**Features**:
19
-
-**Access Management**: Configures and verifies authorities for integrated applications, with database checks to ensure accurate permissions.
20
-
-**Comprehensive Identity Management**: Manages user profiles, permissions, and administrative controls.
21
-
-**Technology**: Developed with **Spring Boot** for robust backend support and efficient data handling.
17
+
- Purpose: ICS focuses on managing identity and access control for both users and administrators.
18
+
- Features:
19
+
- Access Management: Configures and verifies authorities for integrated applications, with database checks to ensure accurate permissions.
20
+
- Comprehensive Identity Management: Manages user profiles, permissions, and administrative controls.
21
+
- Technology: Developed with Spring Boot for robust backend support and efficient data handling.
22
22
23
23
### Shared Database
24
24
25
-
Both CAS and ICS utilize a centralized **Accounts Database** (PostgreSQL), storing essential user data and access control information with durability and security:
25
+
Both CAS and ICS utilize a centralized Accounts Database (PostgreSQL), storing essential user data and access control information with durability and security:
26
26
27
-
-**Account Information**: Holds user profiles and core account data.
28
-
-**Access Authorities**: Manages permissions across Google Club applications to ensure unified, up-to-date access control.
27
+
- Account Information: Holds user profiles and core account data.
28
+
- Access Authorities: Manages permissions across Google Club applications to ensure unified, up-to-date access control.
@@ -36,16 +36,16 @@ The system includes two main Angular-based clients to allow users and administra
36
36
37
37
1.**AMWC (Account Manager Web Client)**
38
38
39
-
-**Audience**: End-users.
40
-
-**Purpose**:
39
+
- Audience: End-users.
40
+
- Purpose:
41
41
- Control over account details.
42
42
- View authorities.
43
43
- Single Sign-On (SSO) access across the ecosystem.
44
44
45
45
2.**ACWC (Accounts Console Web Client)**
46
46
47
-
-**Audience**: Administrators.
48
-
-**Purpose**:
47
+
- Audience: Administrators.
48
+
- Purpose:
49
49
- Identity verification, account management, and authority controls.
50
50
- Granting, revoking, and managing permissions.
51
51
- Analyzing user data and trends.
@@ -54,18 +54,18 @@ The system includes two main Angular-based clients to allow users and administra
54
54
55
55
Each service has dedicated APIs to facilitate requests and operations across the UAS system:
56
56
57
-
# Identity and Access Control Server
57
+
##Identity and Access Control Server
58
58
59
-
-**[ICS API Endpoints](./images/ics-api-endpoints.png)** - Click to view ICS API endpoints in Postman.
59
+
-[ICS API Endpoints](./images/ics-api-endpoints.png) - Click to view ICS API endpoints in Postman.
60
60
61
-
## 1. General Purpose
61
+
###1. General Purpose
62
62
63
63
-**GET**`/health-check`
64
64
Health check for the server.
65
65
66
-
## 2. Account Manager
66
+
###2. Account Manager
67
67
68
-
### 2.1 Account Management
68
+
####2.1 Account Management
69
69
70
70
-**POST**`/create-account`
71
71
Create a new account.
@@ -86,9 +86,9 @@ Each service has dedicated APIs to facilitate requests and operations across the
86
86
-**DELETE**`/delete-my-account`
87
87
Delete the account.
88
88
89
-
### 2.2 Accounts Console
89
+
####2.2 Accounts Console
90
90
91
-
#### 2.2.1 Account Management
91
+
#####2.2.1 Account Management
92
92
93
93
-**GET**`/search-accounts`
94
94
Search for accounts.
@@ -103,7 +103,7 @@ Each service has dedicated APIs to facilitate requests and operations across the
103
103
-**POST**`/lock-account`
104
104
Lock an account.
105
105
106
-
#### 2.2.2 Role Management
106
+
#####2.2.2 Role Management
107
107
108
108
-**GET**`/search-roles`
109
109
Search for roles.
@@ -116,7 +116,7 @@ Each service has dedicated APIs to facilitate requests and operations across the
116
116
-**DELETE**`/delete-role`
117
117
Delete a role.
118
118
119
-
#### 2.2.3 Permission Management
119
+
#####2.2.3 Permission Management
120
120
121
121
-**GET**`/search-permissions`
122
122
Search for permissions.
@@ -131,14 +131,14 @@ Each service has dedicated APIs to facilitate requests and operations across the
131
131
132
132
# Centralized Authentication Service
133
133
134
-
-**[CAS API Endpoints](./images/cas-api-endpoints.png)** - Click to view CAS API endpoints in Postman.
134
+
-[CAS API Endpoints](./images/cas-api-endpoints.png) - Click to view CAS API endpoints in Postman.
135
135
136
-
## 1. General Purpose
136
+
###1. General Purpose
137
137
138
138
-**GET**`/health-check`
139
139
Health check for the service.
140
140
141
-
## 2. Cache Management
141
+
###2. Cache Management
142
142
143
143
-**GET**`/get-all-accounts-ids-in-cache`
144
144
Retrieve all account IDs from cache.
@@ -149,7 +149,7 @@ Each service has dedicated APIs to facilitate requests and operations across the
149
149
-**DELETE**`/clear-account-cache`
150
150
Clear the cache for a specific account.
151
151
152
-
## 3. Authentication Management
152
+
###3. Authentication Management
153
153
154
154
-**POST**`/generate-jwt-token`
155
155
Generate JWT token (login).
@@ -158,7 +158,7 @@ Each service has dedicated APIs to facilitate requests and operations across the
158
158
-**GET**`/verify-token`
159
159
Verify the validity of a token.
160
160
161
-
### System Communication
161
+
####System Communication
162
162
163
163
The UAS architecture supports smooth communication between the CAS, ICS, the shared database, and client interfaces. This integrated design supports real-time updates and centralized control over identity and access management.
Copy file name to clipboardExpand all lines: how_to_integrate.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,3 @@
1
-
# Integrating Your Application with Google UAS
2
-
3
1
Integrating with the **Google Club Unified Access System (UAS)** for authentication and authorization is a straightforward process. Here’s a step-by-step guide to get your app fully integrated with Google Club UAS.
4
2
5
3
For any assistance, please contact the admins at [contact.isetchggl@gmail.com](mailto:contact.isetchggl@gmail.com).
0 commit comments