wso2-am

WSO2 api manager not propagating content type header for multipart form data

走远了吗. 提交于 2019-12-02 05:15:31
问题 I'm using WSO2 api manager 1.10.0. I have a problem when using multipart/form-data , in fact i noticed that content type header isn't propagated to my back end service and so I'm getting unsupported media type 415 HTTP error. Please any idea how to fix this? 回答1: Add the following property to repository/conf/passthru-http.properties file. http.headers.preserve=Content-Type This will preserve the content type header you send with the request and send it to the backend. If you want to preserve

How to integrate WSO2 API Manager (AM) 1.10.0 with PingFederate SAML 2.0?

旧街凉风 提交于 2019-12-02 04:50:23
How to integrate WSO2 am 1.10.0 with PingFederate SAML 2.0? Any instructions? From WSO2 web site, I only saw docs on how to set up SSO among WSO2 products: https://docs.wso2.com/display/AM1100/Configuring+Single+Sign-on+with+SAML2 . But I did not see documentation on how to enable WSO2 AM 1.10.0 with external identity providers such as PingFederate via SAML2. Any help is appreciated. *** UPDATE: I followed the instructions here https://docs.wso2.com/display/AM1100/Configuring+Single+Sign-on+with+SAML2 - just assuming WSO2 IS as PingIdentity. For the mojority part it's working, but I cannot

Unable to publish XACML policy in wso2 application manager and throwing NoSuchMethodError exception

大兔子大兔子 提交于 2019-12-02 04:37:30
I followed the steps provided by the below links to create a policy in the wso2 application manager and publshing http://wso2.com/library/articles/2014/02/use-of-wso2-api-manager-to-validate-fine-grained-policy-decisions-using-xacml/ After created the XACML Policy trying to publish it to PDP,getting the following error [2014-09-15 15:52:53,007] ERROR - ApplicationDispatcher Servlet.service() for servlet bridgeservlet threw exception java.lang.NoSuchMethodError: org.wso2.carbon.identity.entitlement.stub.EntitlementPolicyAdminServiceStub.publishPolicies([Ljava g;Ljava/lang/String;ZI)V at org

How to configure WSO2 API Manager 2.1.0 to work with Identity Server 5.3.0

人盡茶涼 提交于 2019-12-02 04:14:21
问题 I made the whole configuration of this link: https://docs.wso2.com/display/AM210/Configuring+WSO2+Identity+Server+as+a+Key+Manager and now I get this error when I make a request for my API: <ams:fault xmlns:ams="http://wso2.org/apimanager/security"> <ams:code>900908</ams:code> <ams:message>Resource forbidden </ams:message> <ams:description>Access failure for API: /test/1.0.0, version: 1.0.0 status: (900908) - Resource forbidden </ams:description> </ams:fault> Can anybody help me? 回答1:

WSO2 Api Manager - How to change the expiration time of JWT?

时光怂恿深爱的人放手 提交于 2019-12-02 02:45:19
问题 I want to change the expiration time of JWT token created in WSO2 Api Manager. It seems that the default time is 15 minutes. {"typ":"JWT","alg":"none"}. { "iss": "wso2.org/products/am", "exp": 1464255150998, ... } From this link - Wso2 Jira - APIMANAGER-3493 , it seems that we can use "SecurityContextTTL" property in /repository/conf/api-manager.xml under APIKeyManager to change the expiration time of the JWT. But I could not find this setting available in api-manager.xml (not even as a

WSO2 Api Manager - How to change the expiration time of JWT?

萝らか妹 提交于 2019-12-02 02:18:40
I want to change the expiration time of JWT token created in WSO2 Api Manager. It seems that the default time is 15 minutes. {"typ":"JWT","alg":"none"}. { "iss": "wso2.org/products/am", "exp": 1464255150998, ... } From this link - Wso2 Jira - APIMANAGER-3493 , it seems that we can use "SecurityContextTTL" property in /repository/conf/api-manager.xml under APIKeyManager to change the expiration time of the JWT. But I could not find this setting available in api-manager.xml (not even as a commented out configuration). I am using wso2am-1.9.1. Is this property removed from the configurations? If

WSO2 api manager not propagating content type header for multipart form data

醉酒当歌 提交于 2019-12-02 01:38:00
I'm using WSO2 api manager 1.10.0. I have a problem when using multipart/form-data , in fact i noticed that content type header isn't propagated to my back end service and so I'm getting unsupported media type 415 HTTP error. Please any idea how to fix this? Add the following property to repository/conf/passthru-http.properties file. http.headers.preserve=Content-Type This will preserve the content type header you send with the request and send it to the backend. If you want to preserve more such headers, you can add them to the same line with comma separated. 来源: https://stackoverflow.com

ERROR - ListenerManager Couldn't initialize the httpstransport listener - WSO2

£可爱£侵袭症+ 提交于 2019-12-02 01:20:08
问题 I started fresh copy of the WSO2 API Manager 1.8 and get below error for no reason. ERROR - ListenerManager Couldn't initialize the httpstransport listener How can I fix this? 回答1: Check the system hostname by running following command $ hostname try to ping to the output for that hostname. $ ping <output of the hostname command> If that gives an error check the /etc/hosts file. At least it should have a host entry to 127.0.0.1 127.0.0.1 <hostname> or <local ip> <hostname> 回答2: Type root@S-06

ERROR - ListenerManager Couldn't initialize the httpstransport listener - WSO2

☆樱花仙子☆ 提交于 2019-12-01 21:56:10
I started fresh copy of the WSO2 API Manager 1.8 and get below error for no reason. ERROR - ListenerManager Couldn't initialize the httpstransport listener How can I fix this? Check the system hostname by running following command $ hostname try to ping to the output for that hostname. $ ping <output of the hostname command> If that gives an error check the /etc/hosts file. At least it should have a host entry to 127.0.0.1 127.0.0.1 <hostname> or <local ip> <hostname> Type root@S-06:hostname S-06 Type get your IP root@S-06:ifconfig Add it to vim /etc/hosts as a record. 192.168.4.123 S-06 来源:

WSO2 API Manager, is it possible to disable the access-token mechanism

 ̄綄美尐妖づ 提交于 2019-12-01 12:53:35
Is it possible to disable the access-token mechanism in WSO2 API Manager? So we do not have to set the authentication bearer header .I know I can set the access-token time-out to -1 seconds, to make it endless. Yes You can. WSO2 API Manager provides resource level authentication where you can specify the authentication mechanism for each HTTP verb. If you set it to 'None', then you do not need to set Authorization headers when you call the API. As given in the document[1],when creating the API set 'AuthType' value as 'None' for all the HTTP verbs. [1] http://docs.wso2.org/display/AM150/API