[
https://issues.apache.org/jira/browse/FINERACT-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193852#comment-17193852
]
Michael Vorburger commented on FINERACT-1144:
---------------------------------------------
My experiments in FINERACT-1145 shows that it is possible to invoke the REST
endpoint. Whether what that returns can then actually be used is another
question (I don't know how to use it). If it does, then we can close this issue.
> OAuth broken (or is it?)
> ------------------------
>
> Key: FINERACT-1144
> URL: https://issues.apache.org/jira/browse/FINERACT-1144
> Project: Apache Fineract
> Issue Type: Bug
> Components: Security
> Reporter: Michael Vorburger
> Priority: Major
> Fix For: 1.5.0
>
>
> Reading [~avikganguly010] comment in FINERACT-629 that "the spring oauth
> changes we did broke Oauth", and a number of (failed, uncompleted, abandoned)
> PRs by [~saransh] related to FINERACT-1012 and FINERACT-1057 gives me the
> impression that Fineract's OAuth support feature may actually currently be
> broken.
> Let's use this issue for someone to investigate and propose a PR to fix
> Fineract's OAuth support. I see this as a separate issue from FINERACT-1012.
> It would be "fair game", IMHO, to propose to just e.g. revert whatever is
> known to have broken it (if someone knows what that is - I personally do not)
> - and then deal separate and later with respective 3rd party upgrades, or
> whatever.
> If it's not broken and works on develop (and thus 1.4.0) as-is, then this
> issue should be closed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
