I am trying to configure the WSO2 APIM Analytics Ver 3.1 with WSO2 APIM 3.0 in distributed environment, But it is showing "No Dashboards available" in Analytics Dashboard and no error is there in logs.
I am not sure about the configuration i have done in deployment.toml. Please help me in configuring the Analytics with APIM.
Following is the configuration for auth.config in deployment.toml(dashboard):
auth.configs:
type: 'apim'
ssoEnabled: true
properties:
adminScope: apim_analytics:admin_carbon.super
allScopes: apim_analytics:admin apim_analytics:product_manager apim_analytics:api_developer apim_analytics:app_developer apim_analytics:devops_engineer apim_analytics:analytics_viewer apim_analytics:everyone openid apim:api_view apim:subscribe
adminServiceBaseUrl: https://Publisher Server URL
adminUsername: admin
adminPassword: admin
kmDcrUrl: https://Key-Manager Server URL/client-registration/v0.15/register
kmTokenUrlForRedirection: https://Key-Manager Server URL/oauth2
kmTokenUrl: https://Key-Manager Server URL/oauth2
kmUsername: admin
kmPassword: admin
portalAppContext: analytics-dashboard
businessRulesAppContext : business-rules
cacheTimeout: 900
baseUrl: https://Analytics Server URL
grantType: authorization_code
publisherUrl: https://Key-Manager Server URL
storeUrl: https://Store URL
externalLogoutUrl: https://Key-Manager Server URL/oidc/logout
Thanks in advance..!!!
This is a known issue and is fixed with the following Pull Request.
We have already fixed this issue. Please check with the latest released APIM Analytics 3.1.0-m4 release and tell us whether this issue still exists.
Related
I'm unable login into Wso2 APIM and showing invalid login details but yesterday it was working fine and able to login.
Apim version: 3.2.0.
Identity server wso2 is-km: 5.10.0
I have not changed any of the configuration.
My Wso2 APIM is integrated with wso2 Is.
Below error:
2022-03-07 13:58:07,464] INFO - TimeoutHandler This engine will expire all callbacks after GLOBAL_TIMEOUT: 120 seconds, irrespective of the timeout action, after the specified or optional timeout
[2022-03-07 13:58:07,749] ERROR - OAuth2Service Error while finding application state for application with client_id: oYDtSc**************
After that tried logging into Wso2 Identify server with admin as usually but not data it showing like list of users and list of identity providers but previously I saw list of providers etc.
Please help me in this situation.
WSO2 Api manager 3.2.0 Analytics not showing any data.I hit the api many times and try out, but not showing any thing. Its configured successfully as following info :
DataBridge user admin connected
Duplicate of wso2 api mnager analytics dashborad show api name but not usages
If you are using Oracle schemas to configure Analytics in your environment, add the following datasource configuration under ANALYTICS_DB in the Dashboard's <analytics>/conf/dashboard/deployment.yaml
connectionInitSql: alter session set NLS_DATE_FORMAT='YYYY-MM-DD HH24:MI:SS'
A complete configuration will be as following
- name: APIM_ANALYTICS_DB
description: Datasource used for APIM Analytics
jndiConfig:
name: jdbc/APIM_ANALYTICS_DB
definition:
type: RDBMS
configuration:
...
connectionInitSql: alter session set NLS_DATE_FORMAT='YYYY-MM-DD HH24:MI:SS'
Perform the above-mentioned configurations and restart the Dashboard nodes and verify the behavior.
I am running WSO2 APIM 3.2.0 and Analytics 3.2.0 on different client servers. I did all the required settings to configure WSO2 APIM with WSO2 Analytics. Started both the servers successfully and WSO2 APIM URL's open well. But, when I open the Analytics Dashboard URL (https://<Analytics_Host>:9643/analytics-dashboard/login), I get the below warning in the dashboard server logs, and the login page does not appear. Only a blank screen appears.
WARN {org.wso2.msf4j.internal.MSF4JHttpConnectorListener} - Unmapped
exception feign.RetryableException: No subject alternative names
matching IP address <APIM_IP> found executing GET
https://<APIM_Host>:9443/api/am/admin/v0.16/custom-urls/carbon.super
In the browser console I can see errors as shown in the below screenshot.
One more thing I noticed is in the management console of WSO2 APIM, difference in Service Providers list when compared with my local. I didn't find all the service providers on the client server which I can see on my local.
WSO2 APIM Carbon Console Service Providers list on my local:
WSO2 APIM Carbon Console list on the client server:
Am I missing out on some configurations? Need suggestions on this issue.
I have a API Manager 2.6.0 deployment within 3 nodes i.e. 3 VMs. Abbreviations:
GW - Gateway
AIO - Traffic Manager, Key Manager, Dev portal, Publisher
Analytucs - Api M Analytics 2.6.0
DB - PostgreSQL.
I've set everything working between components, till I changed the default admin password, username stood the same.
As per manual I did
Changed the admin password from UI, sice I did a tests already with default credentials
Changed password in api-manager.xml on AIO and GW
Changed password in user-mgt.xml on AIO and GW
Changed password in jndi.properties on AIO and GW
Above 4 points as noted in manual- https://docs.wso2.com/display/AM260/Maintaining+Logins+and+Passwords
This manual does not tell how to make distributed analytics node to accept that password.
The Analytics Install manual told to install WSO2 API-M Analytics and WSO2 API-M(which as I understand is meant if both are on same machine). Again, this manual does not tell much about user configuring on Analytics server.
I tried to look from DAS and SP manual, but the Analytics does not have auth.configs: in YAML files and nor adding them manually from SP source code helps.
Error returned on GW and AIO:
2019-02-21 15:13:52,090 [-] [DataBridge-ConnectionService-tcp://192.168.102.39:7612-pool-11-thread-1] ERROR DataEndpointConnectionWorker Error while trying to connect to the endpoint. Cannot borrow client for ssl://192.168.102.39:7712.
org.wso2.carbon.databridge.agent.exception.DataEndpointLoginException: Cannot borrow client for ssl://192.168.102.39:7712.
Caused by: org.wso2.carbon.databridge.agent.exception.DataEndpointLoginException: Error while trying to login to the data receiver.
Caused by: ThriftAuthenticationException(message:wrong userName or password)
On Analytics obvious:
[2019-02-21 15:16:49,016] ERROR {org.wso2.carbon.databridge.core.internal.authentication.CarbonAuthenticationHandler} - Authentication failed for username 'admin'. Error : 'Invalid_Credentials'. Error Description : 'The login credential used for login are invalid, username : 'admin'.'
[2019-02-21 15:16:49,016] ERROR {org.wso2.carbon.databridge.core.internal.authentication.Authenticator} - wrong userName or password
The question is, how to make WSO2 APIM Analytics(2.6.0) node, which is separated from API Manager, to accept the changed credentials.
Last tought is do I need to connect Analytics to Carbon DB?
You have to add the auth.configs element to the conf/worker/deployment.yaml file, (Please note the password has to be The Base64(UTF-8) encrypted)
auth.configs:
type: 'local'
userManager:
adminRole: admin
userStore:
users:
-
user:
username: admin
password: YWRtaW4=
roles: 1
roles:
-
role:
id: 1
displayName: admin
I want to set up WSO2 APIM login with Github.
I have integrated WSO2 IS with APIM and installed WSO2 IS Github authenticator, then followed the user guide Configuring Github Authenticator to set up Github authenticator. It works for the sample app which mentioned in the doc.
However, when I changed SP to APIM, I got
Error 401 : Authorization Required.
The server couldn't verify that you are authorized to access the requested resource.
Also I have read [Article] How To Setup a WSO2 API Manager Store Login with Google, it seems no more special configuration. Bad thing is I cannot connect Google, I cannot test it. :(
How can I fix this? Any suggestion? Thanks you.
This is because the default roles of the user is internal/everyone, We can update the internal/everyone roles permission or change the default roles in user-mgt.xml
<Realm>
<configuration>
.....
<EveryOneRoleName>everyone</EveryOneRoleName> <!--change it-->
</configuration>
</Realm>
and it will work.