emakas-users is an identity-authorization module that stores user datas, handles their authentications and authorizations according to OAuth 2.0 specification.
Also whith this module, you can restrict your users (members) by that which services (resources) they can use and how can they use it. In addition to this, you can create secrets for your applications that uses spesific resources.

• Overview
  • Run The Application
  • Claims Of Jwt
• Entity Schemas
  • Fields of Users
  • Fields of Teams
  • Fields of Applications
  • Fields of Resources
  • Fields of Resource Permissions
• Enum Schema
  • Values of Permission Target Type
  • Values of Permission Scopes
  • Values of Access Modifiers
• Endpoint Documentation
  • Application
  • Auth
  • Members
  • OAuth
  • Pages
  • Resource Permissions
  • Resources
  • Teams
  • User

Before run the application, you need to generate two files in order to configure the app

1. Create file named application.yml under src/main/resources/ directory and fill it as follows:

    app:
      domain: iam.emakas.net
    java-jwt:
      secret: YOUR SECRET HERE
      issuer: YOUR ISSUER HERE
      expiration: EXPIRATION TIMES IN SECONDS
    spring:
      datasource:
        url: jdbc:postgresql://DB_URL/DB_NAME
        username: DB_USERNAME
        password: DB_PASSWORD
      jpa:
        hibernate:
          ddl-auto: none
        properties:
          hibernate:
            dialect: org.hibernate.dialect.PostgreSQLDialect

2. Create file named .env inside root directory of project in order to configure database

   DB_PASSWORD=DB_PASSWORD
   DB_NAME=DB_NAME
   DB_USER=DB_USER_NAME
   

3. You can create docker image with command:

   docker build -t emakas-users .

4. After creation, you can start

• iss: Issuer of this token
• sub: Unified Unique Id for user that requested
• exp: Timestamp of expiration date
• aud: Audience claim that describes which domains will use this token

An example Jwt is as folows

{
  "sub": "usr:2dc77664-03fc-4bf9-a46f-e97dd1d8c752",
  "aud": "emakas.net",
  "scope": [
    "global:read_write:iam.emakas.net/resources",
    "team:read:iam.emakas.net/members",
    "self:write:iam.emakas.net/teams"
  ],
  "iss": "emakas-user",
  "exp": 1748544968,
  "iat": 1748544668
}

Applications are way to consume service resources through non-user interactions.
You may want to use your bots, apps or websites to consume your resources such as blog posts, commercial products and so on.
To accomplish this securely, you need to register your apps, bots etc. to this service as Application and give them permissions and restrictions to define which services they can use

POST /api/auth/sign-in

This endpoint is using for signin users in. It should not be use by applications directly. It has XSS protection. To sign users into your systems, you need to redirect users to User Sign Page

GET /page/auth/login?public_key=string&redirect=base64_string

This is the static page that users can log in and redirect to their systems. You need to insert these query parameters in order to use it for your external services. If you don't, user will redirect to dashboard page.