Dear developers,
I want to secure an STS with an issued token over the transport layer (i.e., an
STS Client sends a RequestSecurityToken to the STS with a SAML assertion in the
security header for authentication).
It found wso2-rampart has the following implementation for SAML assertion:
The WSO2 API Manager team is pleased to announce the release of API Manager
3.0.0-M31. It's now available to download.
## *Distribution*
- [wso2apim-3.0.0-m31](
https://github.com/wso2/product-apim/releases/download/v3.0.0-m31/wso2apim-3.0.0-m31.zip
)
## *Documentation*
- [WSO2 API Manager
@Thilini Shanika
On Fri, Oct 19, 2018 at 3:20 PM Godwin Shrimal wrote:
> Hi APIM Team,
>
> We can't see gateways in API Store Console when we use type as production
> and sandbox. If we use both gateways as hybrid then I can see the API
> Gateways in the swagger console.
> Is it a known issue?
On Fri, Oct 19, 2018 at 10:30 AM Uvindra Dias Jayasinha
wrote:
> Here is my take on this. When I originally designed the schema I wasn't
> taking into consideration any of the practical implications associated with
> API resources being saved and retrieved at DB level. But now that we are at
>
Hi,
I'm trying (With EI 6.4.0) to create an operation for a db query where the
input param *SQLType* is defined as an *ARRAY*. Following are the query
details.
*SQL:* SELECT ORDER_ID FROM ROLE_ORDER WHERE ROLE IN (:Roles)
Input Mappings
*Mapping Name* *Parameter Type* *Type* *Action*
Roles
Hi Nuwandi,
The parameter type should be set as ARRAY instead of SCALAR if you want to
input an array. For example,
However the NPE should be fixed. Can you create an issue for that.
In the request you can send the payload as in [1]
[1]
Valid types are "production", "sandbox" and "hybrid". Are you using one of
these or something called "production and sandbox"?
On Fri, Oct 19, 2018 at 9:11 PM Harsha Kumara wrote:
> @Thilini Shanika
>
> On Fri, Oct 19, 2018 at 3:20 PM Godwin Shrimal wrote:
>
>> Hi APIM Team,
>>
>> We can't
Hi Godwin,
Further, if you don't have more than one gateway environments defined under
a given type (production, sandbox, or hybrid), API Gateway drop-down won't
be showing up in API console, since you don't have multiple gateway
endpoints to select in the drop down. That is by design and not a
Hi APIM Team,
We can't see gateways in API Store Console when we use type as production
and sandbox. If we use both gateways as hybrid then I can see the API
Gateways in the swagger console.
Is it a known issue?
Thanks
Godwin
--
*Godwin Amila Shrimal*
Associate Technical Lead
WSO2 Inc.;
Hi Sahan,
Two concerns here:
1. Is the placement of the feature in the menu correct?
2. I don't know if it was intensional, but isn't it better to avoid
InCommon logos and only label it using standard federation terminology?
Because we haven't done it like that so far for other profiles such as
10 matches
Mail list logo
