Description
We have a number of open issues related to apparent OAuth support in Fineract.
There is 0 documentation available on the Apache Fineract project Git repo or Wiki. (One can "deduct" that it can be activated by -Psecurity=oauth at build - but then what?)
IMHO it would be valuable both for end users deployment, integrators and new and old contributors to the project to have this feature documented.
So the goal of this issue is to have comprehensive documentation about Fineract's OAuth support in https://github.com/apache/fineract/tree/develop/docs/deployment/security.md.
This feature may be (apparently?) actually currently be broken on the develop branch as of today (and in 1.4.0), see FINERACT-1144, but that shouldn't someone from contribution documentation of how it should work. That documentation should be able to be followed e.g. on 1.2.0 or 1.3.0 (but I think that's broken due to FINERACT-755, so build 1.3.1 from git).
saransh or aleks or avikganguly010 or josenavarro would any of you like to contribute such documentation to this wonderful project?
PS: Once there is documentation, someone could then build an IT - that's unlocking FINERACT-1143.
Attachments
Issue Links
- Blocked
-
FINERACT-1305 Release Apache Fineract v1.5.0
- Resolved
- is required by
-
FINERACT-1142 Recommend OAuth security for production installations
- Open
-
FINERACT-1033 Fineract OAuth Token Change Bug
- Open
-
FINERACT-1012 Spring Security OAuth 2.x to Spring Security 5.2.x
- Resolved
-
FINERACT-1057 Running -Psecurity=oauth leads to memory leak issue
- Closed
-
FINERACT-1144 OAuth broken (or is it?)
- Closed
-
FINERACT-629 Authentication API endpoint forces username and password as URL params
- Resolved
-
FINERACT-1143 Add Test Coverage for OAuth Support
- Resolved
- links to