The document describes an NBOS API server that uses NBOS IDN for authentication. It includes modules that connect to an IDN server to validate user tokens. The IDN server handles user signup, social logins, and retrieving user roles and authorities. It also describes API endpoints for a public/user todo module that allows getting, creating, and updating todo items. It discusses token validation workflow and caching, as well as multi-tenancy and how apps identify tenants. It provides an example of tenant creation and adding client credentials. It also covers how a new module identifies tenants and verifies tokens using its own credentials.

1. NBOS API Server
REST API Server using NBOS IDN

2. iOS/Android/Desktop APP
Module 1 Module2IDN SERVER
Validate <UserToken>
USER
ROLES AUTHORITIES
SOCIAL_ACCOUNT
IDN SDK
/oauth/token
/api/identity/v0/users/signup
/api/identity/v0/auth/social/facebook/login
Public /User Todo - GET - /api/todo/v0/todos
Create - POST - /api/todo/v0/todos
Update– PUT - /api/todo/v0/todos/id

3. Writing Your Own Endpoints

4. Public/User Todo

5. Create Todo

6. Modify Todo

7. Who is validating user token?

8. Module API Server Workflow

9. Endpoint Token validation

10. Cache Token Verification

11. Multi Tenant ...

12. USER
ROLES AUTHORITIES
SOCIAL_ACCOUNTUSER
ROLES AUTHORITIES
SOCIAL_ACCOUNT
USER
ROLES AUTHORITIES
SOCIAL_ACCOUNT
NBOS IDN SERVER
NBOS IDN Multi Tenancy

13. How apps identify Tenant?
 [
 'client'=>'devConsole-app-client',
 'secret'=>'devConsole-app-secret’
 ]
After Tenant creation, one has to create client credentials.
Apps connect NBOS IDN Server using client credentials.

14. Creating New module in NBOS?

15. How module API Server identity
Tenant?
Just like Tenant, every module has it own credentials and also a module secret key.
These credentials needs to be added in Module API Server Configuration File.
Module API Server verifies a incoming token using these
credentials and in response it gets TenantId and UserId.

16. Thanks