wso2 / wso2/docs-mi

Need to update all EI to MI migration documents on org.wso2.carbon.security.util.ServerCrypto

Open
#877 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area/MigrationDocs Type/Improvement
Dominant language
CSS
Stars
15
Forks
118
Avg merge
8d 4h
Merged PRs (30d)
32

Description

Description

In the EI 6.1.1 to MI 4.2.0 migration document[1] we have not mentioned about changing the org.wso2.carbon.security.util.ServerCrypto to org.wso2.micro.integrator.security.util.ServerCrypto in WSpolicy files. According to the latest documentation we have mentioned changing the org.wso2.carbon.security.util.ServerCrypto to org.wso2.micro.integrator.security.util.ServerCrypto to avoid the no class found issue. [2]
This needs to be updated in all EI to MI migration documents.

[1].https://github.com/wso2-enterprise/migration-docs/blob/main/api-manager/migration-docs/apim/apim-4.2.0/mi/upgrading-from-ei-6.1.1.md
[2].https://mi.docs.wso2.com/en/latest/develop/advanced-development/applying-security-to-a-proxy-service/

Describe the problem(s)

A detailed description of the purpose of this improvement.

Describe your solution(s)

A detailed description of how this improvement will solve the problem described above.

Related issue(s) (optional)

Any related issues such as sub tasks and issues reported in other repositories (e.g., component repositories), similar problems, etc.

Suggested label(s) (optional)

Optional comma-separated list of suggested labels. Non committers can’t assign labels to issues, and thereby, this will help issue creators who are not a committer to suggest possible labels.

Suggested assignee(s) (optional)

Optional comma-separated list of suggested team members who should attend the issue. Non committers can’t assign issues to assignees, and thereby, this will help issue creators who are not a committer to suggest possible assignees.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked EI 6.1.1 to MI 4.2.0 migration document and compare its WSPolicy guidance with the referenced security documentation. Search the repository for all EI-to-MI migration documents and the old org.wso2.carbon.security.util.ServerCrypto reference. Done means each relevant document identifies the org.wso2.micro.integrator.security.util.ServerCrypto replacement.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.