In our project, Client has their own KDC server and client want our WSO2 should talk to client KDC for authentication. I know that how to enable kerberos in WSO2 but I am not able to established connection between our WSO2 to client KDC server(In short, i want to connect WSO2 identity server to external KDC server).
We do not support this in the currently released versions of the WSO2 Identity Server. However, we have successfully done an implementation of authentication with an external KDC for Identity Server 5.3.0 release.
You might be able to test this with the next milestone release of Identity Server.
Related
How do I upload the API I created in WSO2 Integration Studio installed on my own computer to the WSO2 API Manager on the remote server.
From the Add new server menu, I clicked the WSO2 Remote Server option under WSO2 and entered the host and server URL information, but it did not publish. When I examined WSO2's own documents, I could not find detailed resources about connecting to a remote server and publishing.
Can you help with this?
Can you add your integration studio version and WSO2 Api Manager version?
You can try this documentation https://apim.docs.wso2.com/en/latest/integrate/develop/working-with-service-catalog/
You can register the service in the service catelog as below.
Start the WSO2 Micro Integrator pointing to API Manager.
You should have the carbon app of that particular service in the Micro Integrator.
When Micro Integrator starts it registers the available services in the API Manager.
From logging into the APIM publisher you can create an API.
Instructions are available here - https://apim.docs.wso2.com/en/latest/integrate/develop/working-with-service-catalog/
How to connect a server that run wso2 API manager to show statics on a server that run wso2 analytics that actually exist on differnt servers with different IP.
I am using version 3.2.0
You can follow the documentation and configure analytics for APIM 3.2.0.
In the configurations, instead of using localhost, use the IP address of the analytics server.
https://apim.docs.wso2.com/en/3.2.0/learn/analytics/configuring-apim-analytics/#configuring-apim-analytics
I have both my wso2 api manager and wso2 identity server running on the same instance .So I wanted my wso2 identity server to run at port 9444. I restarted my wso2 identity server after adding an offset of 1 in the carbon.xml.
I am getting a 502 Bad gateway error when I try to access my carbon console on 9444 port or any other port.
Are there other places where I need to change the port in the wso2 identity server. I have not changed the port settings in any other config files in the identity server .They are still showing the default port settings
You have to change only port offset in carbon.xml for WSO2 Identity Server. Have a look [1]
[1] https://docs.wso2.com/display/IS570/Default+Ports+of+WSO2+Products
I want to connect WSO2 IOT Server to WSO2 IS Server for user authorization. Is there any way to connect WSO2 IOT Server to WSO2 IS Server.
You can use the IS as a key manager by following the docs https://docs.wso2.com/display/CLUSTER44x/Configuring+the+Identity+Server+5.2.0+as+a+Key+Manager+with+API+Manager+2.0.0
In addition to above there are few IoT related feature that needs to be installed in the IS[1]
[1] https://github.com/wso2/carbon-device-mgt/tree/master/features/oauth-extensions
I am working with WSO2 Identity Server 5.0.0 and tried a client library (oxRay) to utilize its OpenID Connect capabilities.
However, it seems that the request to the discovery URL https://myserver/.well-known/openid-configuration doesn't return anything reasonable. So the OIDC client fails to work properly.
Is Identity Server supporting OIDC discovery or did I miss something in the configuration?
WSO2 Identity Server does not support OIDC Discovery at the current releases.
WSO2 Identity Server 5.3.0 does support OpenID Connect Discovery.
From the release notes (emphasis mine):
OAuth 2.0/Open ID Connect Enhancements:
Open ID Connect Dynamic Client Registration. For more information, see OpenID Connect Dynamic Client Registration.
OAuth 2.0 Token Introspection. For more information, see Invoke the OAuth Introspection Endpoint.
Open ID Connect Discovery support. For more information, see the Open ID Connect specification.
However, I do seem to have run into an issue when trying to use it.