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

Port fixes for wso2-extensions/identity-inbound-auth-oauth #2406

Closed
Tracked by #2404
RusJaI opened this issue Jan 23, 2024 · 5 comments
Closed
Tracked by #2404

Port fixes for wso2-extensions/identity-inbound-auth-oauth #2406

RusJaI opened this issue Jan 23, 2024 · 5 comments
Assignees

Comments

@RusJaI
Copy link

RusJaI commented Jan 23, 2024

Need to apply relevant fixes into https://github.com/wso2-extensions/identity-inbound-auth-oauth/tree/6.9.x

@RusJaI
Copy link
Author

RusJaI commented Jan 24, 2024

Update [2024-01-23]

Started working on the issue after completing the commits doc, which contains the PRs for each identity component.

There are some commits that are already there in the corresponding master branch.

Completed adding commits from support PRs.

@RusJaI
Copy link
Author

RusJaI commented Jan 24, 2024

Update [2024-01-24]

As per the README of the carbon identity inbound oauth repo, it should be able to build on jdk 11 and 17.

But the build is failing with both jdk versions and with jdk 8, it builds with errors of finding resource paths.

Checked the same issue in previous release checking out to tag 6.9.6. The same issue exists there as well.

Currently analysing the issue.

@RusJaI
Copy link
Author

RusJaI commented Jan 28, 2024

Update [2024-01-25]

As per the Jenkins build it supports JDK 11 and Maven 3.5.4
It was identified that this issue is a known issue for Mac OS (with Apple Silicon)

Further when analysing the corresponding patch entries for the applied commits, identified that some fixes are going to several repositories. Hence the fix to be fully applicable, need to apply the changes into corresponding branches of those repositories too.

Other than that, have to check whether there are fixes which porting has not been done into 6.9.x branch.

Currently analysing that fixes and documenting them. This is stacked by : #2428

@RusJaI
Copy link
Author

RusJaI commented Jan 30, 2024

Update [2024-01-30]

As mentioned in the comment : #2428 (comment), since it was decided to change the kernel version, the component version for this repository will be changed to 6.11.x

Related work to this issue will be started after initial analysis and related kernel fixes.

@HiranyaKavishani
Copy link

Closing the issue as the task is done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants