Tide launches a feature which facilitates the login of old users using the new service with leverage the high security provided by the Gravitee

Industry

Technology

AWS Fargate Cluster AWS S3 AWS SNS Java 11 JOOQ MySQL Database Spring Security

Introduction

NashTech helps Tide create new endpoints that enables legacy users to easily port into the gravitee and access all other endpoints.

About Tide

Tide (Tide Platform Limited) is a UK financial technology company providing mobile-first banking services for small and medium-sized enterprises. It enables businesses to set up a current account and get instant access to various financial services (including automated bookkeeping and integrated invoicing).

Challenges

In Tide legacy users (i.e. users created without the Gravitee AM) have no access to the new system as they do not do the Oauth journey which was implemented to the new users. So to make this possible, legacy users need to be ported to the new system (Gravitee).

Solution

Tide has two types of users: “Team member users’ ‘ and “Legacy users.” Team member users are those users who exist in gravitee. Legacy users are those users who don’t exist in gravitee. The users only exist in the old system; for that, we have created a new endpoint that checks whether the user exists in gravitee or not. This endpoint is hit before login in the Legacy users; if that user does not exist in the gravitee then that endpoint port that user into the gravitee and maintains a mapping for those users into the table, if the system needs LegacyId so we can easily find out that Id using the id created by the gravitee.

Get an access token they can use with the onboarding API (This token is basically a JWT token that is generated using the signature algorithm RS256).
Get their user added to the TIDE IAM system with a membership of the company they are completing an application form so that they can log back into it later.
Once all details are provided by the applicant and all the check results have been received, call the Decision Engine.
If the application is approved by the decision engine User is updated in user-management-service (UMS).

Results

All the legacy users easily port into the gravitee.
Now legacy users easily access all the other endpoints.
Maintaining legacy users mapping which identifies that particular users are legacy users or team members.