Versions Compared

Old Version 4

changes.mady.by.user Former user

Saved on

compared with

New Version 5

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Fixed formatting

Table of Contents

...

Why are the changes I did to the  Response Content Type  resource parameter of a published API not reflected in the API Store, even after saving?

If you edited the Response Content Type using the UI, please open the API's Swagger definition, do your changes, and save. Then the changes should be reflected back in the API Store. This will be fixed in a future release.

...

You can protect your server from attacks such as the Logjam attack (Man-in-the-Middle attack) by disabling weak ciphers. For more details, see  Disable weak ciphers in the WSO2 Admin Guide.

...

  • Did you change the default admin password?
    If so, you need to change the credentials stored in the <APIKeyValidator> element of the <APIM <API-M_HOME>/repository/conf/api-manager.xml file of the API Gateway node/s.

  • Have you set the priority of the SAML2SSOAuthenticator handler higher than that of the BasicAuthenticator handler in the authenticators.xml file?
    If so, the SAML2SSOAuthenticator handler tries to manage the basic authentication requests as well. Set a lower priority to the SAML2SSOAuthenticator than the BasicAuthenticator handler as follows:

    Code Block
    languagexml
    <Authenticator name="SAML2SSOAuthenticator" disabled="false">
   <Priority>0</Priority>
   <Config>
      <Parameter name="LoginPage">/carbon/admin/login.jsp</Parameter>
      <Parameter name="ServiceProviderID">carbonServer</Parameter>
      <Parameter name="IdentityProviderSSOServiceURL">https://localhost:9444/samlsso</Parameter>
      <Parameter name="NameIDPolicyFormat">urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</Parameter>
      <Parameter name="ISAuthnReqSigned">false</Parameter>
      <!-<Parameter name="AssetionConsumerServiceURL">https://localhost:9443/acs</Parameter>->
   </Config>
</Authenticator>

...

Update the <Password>, <KeyAlias>, <KeyPassword> values under the <KeyStore> field in the <API-M_HOME>/repository/conf/carbon.xml file based on your new key store configuration.

...

The root cause for the javax.net.ssl.SSLException: Received fatal alert: unknown_ca error is because the default pack is not shipped with a CA-signed certificate. When using the API Console, the web browser sends an HTTPs request to the API Gateway. As the certificate on the Gateway is not CA-signed, the browser does not accept it.

To resolve this issue, first access the Gateway URL via a new browser tab of the same browser and accept the certificate from the browser. 

...

Tip

If you are using the API-M instance you used as the first instance in the Publish through Multiple API Gateways tutorial, you may receive the above error when trying out other tutorials. This is because you updated the environments configurations in that pack by adding two API Gateway environments under the <Environments> element,  and commenting the <environment> element that comes by default. To overcome this error, uncomment the default configuration and delete the newly added configuration under <Environments> in the <API-M>/repository/conf/api-manager.xml file.

How can I capture the state of a system?

...