Details
-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
MCP Service Team 1 Sprint 2
Description
Why
In order to implement the SDK for the IDM service, there are a few options. We need to make a decision on which approach we will take.
What
Options to consider are:
- Option 1 - Use an existing 3rd party implementation
- Pros
- Small amount of work required.
- Opportunity to contribute to the open source project
- Cons
- No control over the priority of feature delivery
- Pros
- Option 2 - Create our own SDK, but it will depends on an existing 3rd party implementation
- Pros
- Relatively less amount of work
- Full control of the features
- Can change 3rd party lib without impact on the users
- Cons
- Need to make sure the user's app is not using a conflicting 3rd party lib
- Pros
- Option 3 - Eat our own dog food
- Pros
- Full control of the features
- No dependency on 3rd party lib
- Fully target towards our own usecase
- Cons
- A lot of work
- Potentially re-invent the wheel?
- Pros
The decision from this should apply for all the service SDKs, not only just the IDM service SDK.
How
Create a proposal to https://github.com/aerogear/proposals/pull/8 and recommend option 2.
The 3rd party library we are going to use is AppAuth:
https://github.com/openid/AppAuth-android
Attachments
Issue Links
- blocks
-
AEROGEAR-4324 Implement the login function for the Android IDM SDK
- Resolved
-
AEROGEAR-4315 create high level designs for the IDM client SDKs
- Closed