Description:
Solr indexing fails if the property value cannot be parsed to the defined type such as INT, DOUBLE etc. Moreover, long type values are parsed as INT type.
Better to default to string type and support indexing if parsing fails.

Suggested Labels:
Type/Bug

Suggested Assignees:

Affected Product Version:

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Description:
Create special character role and assign it to store user, then login to store to view list of API give error.

Affected Product Version:
APIM 2.1.0

Steps to reproduce:

1. Create a role with a special character (Eg: test:new)
2. Add the created role to a store user.
3. Login to the store to list the APIs and the error will be logged in the console.

Description:
in jenkins build, SolrClientTestCase is failing due to bytecode validation error. we are currently disable the testcase till we fix the issue. This issue to track the failure.

Suggested Labels:
bug

Suggested Assignees:
daneshk

OS, DB, other environment details and versions:
Jenkins environment

Description:
IndexingHandler is to create indexes for created and updated resources. So that changes are shown in the UI immediately rather waiting till indexing process execution. We don't need to do indexing through handler for the registry operations such as move,copy and rename. those will handle by the indexing process.

Suggested Labels:
improvement

Suggested Assignees:
daneshk

Affected Product Version:

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Description:

• Login to the Governance Registry management console and Goto Extensions -> Handlers -> Handler Simulator.
• Select operation type as get
• Select any registry path
• Click on simulate.

Expected behavior:
Simulated handler chain will be shown in UI

Actual behavior:
Internal Server error throws as below,

Suggested Labels:
bug

Suggested Assignees:
@daneshk

Affected Product Version:
5.4.0

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Description:
Wso2 orbit contains a new version of httpclient pointing to httpclient-4.3.6

Suggested Labels:

Suggested Assignees:

Affected Product Version:

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Description:
When storing a value with a comma in the registry, when making a GET request to the endpoint "/resource/1.0.0/properties" it returns an array with two values.

Example use case is when an organization name that contains a comma is stored. For instance, when the value "MyCompany, ltd." is wanted to store for the name "Org_Name", the request's response contains something like this:
{ "name": "Org_Name", "value": [ "MyCompany", " ltd." ] }

Suggested Labels:
Bug

Suggested Assignees:
nadeeshanip

Description:
carbon-registry repo points to an older apache-zookeeper orbit version

Suggested Labels:

Suggested Assignees:

Affected Product Version:

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Description:
a handful of locations still import the old securevault artifact, which has a transitive production dependency on old versions of JUnit (via serp). This causes headaches when trying to test dropins extending e.g. RandomPasswordGenerator

Affected Product Version:
master, 4.4.27

Steps to reproduce:
mvn dependency:tree | less, search for junit.
See also the usages links for the old securevault

Description:
Endpoint Handler should be Unit Testable

Suggested Labels:

Suggested Assignees:
@daneshk

Affected Product Version:

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Description:
When indexing the unbounded tables and fields, indexer should consider this as multi valued fields. but current implementation, it is not considered in certain scenarios.

Suggested Labels:

Suggested Assignees:
@daneshk

Affected Product Version:

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Description:

When there are multiple tenants and all their stores are accessed one by one, a memory leak occurs.

Affected Product Version:

APIM 2.1.0

Steps to reproduce:

1. Create multiple tenants on APIM 2.1.0

2. Reduce the time provided for LazyLoading IdleTime in carbon.xml (will quicken the tenant loading and unloading)

    <LazyLoading>
        <IdleTime>2</IdleTime>
    </LazyLoading>
   

3. Access the stores of all tenants (without login) and observe the growth memory.

Description:
When there is more than 100 user roles created in the system, Registry UI won't display roles added later in the drop down combo box.

Suggested Labels:
Bug

Affected Product Version:
EMM-2.2.0, registry 4.5.8

OS, DB, other environment details and versions:
Reproducible with all DB versions and environments

Steps to reproduce:

1. Add mode than 100 roles in to the system
2. Browse and select any registry resource via carbon console
3. Expand permissions section
4. Search for role names which added after first 100 of roles

I'm using:

import org.wso2.carbon.registry.app.RemoteRegistry;

RemoteRegistry remoteRegistry = new RemoteRegistry("https://localhost:9443/registry", "admin", "admin");
String res = remoteRegistry.put("/home", remoteRegistry.newCollection());
System.out.println(res);

The result I get is:

/atom/home

However, I expected to get:

/home

Why is the /atom part prepended automatically to the returned value?
When I browse the WSO2IS management interface I see the correct "/home" collection created, without the "/atom" prefix.

The documentation of the "put" method says:
@return the actual path that the server chose to use for our Resource, When an handler is used for the put operation the actual path needs to be set properly within the handler

So the "actual path" returned should be "/home", not "/atom/home".