enter image description here
Data Mapper Configuration is appearing null in wso2
You need to have a Registry Resources project created, to save the Datamapper configuration.
https://ei.docs.wso2.com/en/latest/micro-integrator/develop/create-integration-project/#integration-project
https://ei.docs.wso2.com/en/latest/micro-integrator/references/mediators/data-Mapper-Mediator/
Related
I have been trying to setup the WSO2 API Manager in a distributed setup. I have made all the configurations and it got started. But when I changed the key store by creating a new key store, the Traffic manager and other profiles are not getting started. I am getting the below error while starting the different profiles of API Manager after setting up the key store.
Caused by: java.lang.IllegalArgumentException: jsse.alias_no_key_entry
at org.apache.tomcat.util.net.AbstractJsseEndpoint.createSSLContext(AbstractJsseEndpoint.java:99)
I followed this link - https://apim.docs.wso2.com/en/latest/install-and-setup/setup/security/configuring-keystores/keystore-basics/creating-new-keystores/#adding-ca-signed-certificates-to-keystores for setting up a new key store.
Thanks in advance.
alias should be wso2carbon, if you change it you have to change alias name in config
I changed the datasource from H2 to MSSQL, and WSO2 AM created the admin user. I created the endpoints, but when I restart the container (because I changed the port), WSO2 AM is in blank, but the database has the information user, endpoint, etc. how can I use the same information of the database in WSO2 AM.
Thanks
"WSO2 AM is in blank, but the database has the information user, endpoint, etc. how can I use the same information of the database in WSO2 AM." : What do you mean by here? Once you changed the database (H2 -> MsSQL) can't you see any created APIs in the publisher or store UI? If it is, did you migrate the H2 data from MsSQL database(AM DB data, Registry DB data and UM dB data)? If you have migrated data, in order to see the API in Publisher and Store UI, you can do the reindexing as mentioned here(5th step)[1]
[1]. https://docs.wso2.com/display/AM260/Upgrading+from+the+Previous+Release#UpgradingfromthePreviousRelease-Step2-UpgradeWSO2API-M2.5.0to2.6.0
I am using wso2is-km-5.9.0 for serving our application authentication and SSO needs and we have coupled wso2is-analytics-5.8.0 with our Identity Server. I have followed the steps mentioned in the offical documentation i.e setting Analytics in api-manager.xml to True and enabling the eventpublishers but I'm unable to see any data in Analytics dashboard. Please refer the error logs for the same attached.
Why is the data not being populated in WSO2 analytics dashboard??
Analytics error log
Identity Server error log
With the new config model introduction, you should not edit the api-manager.xml file. It should be done via deployement.toml file.
Moreover you have to enable event listeners and publishes in deployment.toml file. This will enable publishing data to the analytics. You should refer the documentation in https://is.docs.wso2.com/en/5.9.0/learn/configuring-identity-analytics/ because IS and IS-KM is more similar, difference is having an apim-manger.xml file.
[[event_listener]]
id = "authn_data_publisher_proxy"
type = "org.wso2.carbon.identity.core.handler.AbstractIdentityMessageHandler"
name = "org.wso2.carbon.identity.data.publisher.application.authentication.AuthnDataPublisherProxy"
order = 11
[identity_mgt.analytics_login_data_publisher]
enable=true
[identity_mgt.analytics_session_data_publisher]
enable=true
We have done WSO2 IS configurations with multiple LDAPs with multiple clients successfully before. This time with a new client we are getting an error as show in image. "Error occured while getting all user claims for ... in carbon.super.
The case is we have created a service and mapped custom claims to map to LDAP. The issue is with a field mapped with http://wso2.org/claims/role attribute . If we remove this attribute from the custom claims the error goes away.
But we are using roles in business logic(Internal roles created in WSO2) which we get as null in case we remove this attribute.
We want to know the solution. Is there some change required at LDAP side ? Or how we can achieve the roles without mapping as a claim with LDAP?
I read the post at WSO2 API Manager and XACML Entitlement which says that a configuration file in API Manager can be modified to use an entitlement mediator in "the in sequence".
I know how to edit this configuration through the web interface. But which file contains this configuration?
This configuration doesn't have a element or element (except for the elements in elements). Exactly where should I put the element?
If I create my own entitlement mediator, how do I plug it in or make it available to the API Manager?
Go to APIM distribution,HOME\repository\deployment\server\synapse-configs\default\api folder,where you will see the api configurations, which you create from publisher. Add your mediator there, by editing the configuration and restart the server.