Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client registration with custom security #2

Merged
merged 10 commits into from Jun 3, 2019
Merged

Commits on May 29, 2019

  1. Client Model Class Added

    rahul-y committed May 29, 2019
    Configuration menu
    Copy the full SHA
    06b7edb View commit details
    Browse the repository at this point in the history

Commits on May 31, 2019

  1. client-registration added

    rahul-y committed May 31, 2019
    Configuration menu
    Copy the full SHA
    c4d8a0c View commit details
    Browse the repository at this point in the history

Commits on Jun 2, 2019

  1. Custom password encoder added

    This overrides encode and matches method of default password encoder provided by spring security.
    rahul-y committed Jun 2, 2019
    Configuration menu
    Copy the full SHA
    44269d5 View commit details
    Browse the repository at this point in the history
  2. Improved security - added custom encryption algorithms

    Contains methods to encrypt the data password using AES algorithm ,SHA1 algorithm and hex encoder ,decoder.
    rahul-y committed Jun 2, 2019
    Configuration menu
    Copy the full SHA
    dee8f45 View commit details
    Browse the repository at this point in the history
  3. Configurations modified to use our custom password encoder

    Both client service and user service will use our custom password encoder to encode credentials before storing in database and also during authentication process.
    rahul-y committed Jun 2, 2019
    Configuration menu
    Copy the full SHA
    8ebce6c View commit details
    Browse the repository at this point in the history
  4. Client registration modified

    Now client registration end point will only return client_id and client_secret in the encrypted format and also will require only client_name, website_url and redirect url as parameters.
    rahul-y committed Jun 2, 2019
    Configuration menu
    Copy the full SHA
    44ed953 View commit details
    Browse the repository at this point in the history
  5. Sql scripts updated

    Both sql scripts updated to make new columns for client_name and website_url.
    rahul-y committed Jun 2, 2019
    Configuration menu
    Copy the full SHA
    7de8b99 View commit details
    Browse the repository at this point in the history
  6. Fix /oauth/check_token endpoint

    Passed authorization successfully.
    rahul-y committed Jun 2, 2019
    Configuration menu
    Copy the full SHA
    ed013e8 View commit details
    Browse the repository at this point in the history
  7. Client registration process added

    Testing with password grant type removed and registration of a new client added.
    rahul-y committed Jun 2, 2019
    Configuration menu
    Copy the full SHA
    fbf4ab1 View commit details
    Browse the repository at this point in the history

Commits on Jun 3, 2019

  1. Update README.md for client registration

    Replace paramter with json body for the client registration POST request.
    rahul-y committed Jun 3, 2019
    Configuration menu
    Copy the full SHA
    00c0ed5 View commit details
    Browse the repository at this point in the history