Hi All,
As per the offline discussion today, we going to implement according to
following way.
*Rest Apis expose*
/apis/{apiId}/scopes - POST to Create Scope object.
/apis/{apiid}/scopes - GET Get list of scope names
/apis/{apiid}/scopes/{name} - GET get the detail of Scope
@Bhathiya,
We are not giving sharing the scopes between APIS as those roles can have
different definitions as below.
For API1 for resource /menu post need scope1 which have role1 and role2.
For API2 for resource /abc POST need scope1 which have role3 and role4.
therefore we can't create scope
Yes, it will be good to keep the scopes in swagger. As Viduranga pointed
out, we can avoid the security concern as well. (Even though the SDK cannot
be used without a token)
Thanks.
On Tue, Dec 5, 2017 at 8:50 AM, Viduranga Gunarathne
wrote:
> Hi Tharindu,
>
> +1 to keep
Hi,
I think we need to keep scope to role/permission mapping as well which
can't be kept in the swagger definition. We will need to keep that
separately. The approach 1 looks good to me (having a separate /scope
resource)
Thanks!
On Tue, Dec 5, 2017 at 8:50 AM, Viduranga Gunarathne
Hi,
On Tue, Dec 5, 2017 at 9:03 AM, Johann Nallathamby wrote:
> Hi Indunil/Isura,
>
> I have a general comment on this. Are we not planning to support this in
> the UI at least in the public release? Because planning for backend only
> IMO is not a good idea from previous
HI,
On Tue, Dec 5, 2017 at 8:15 AM, Isura Karunaratne wrote:
> Hi Indunil,
>
>
>
> On Mon, Dec 4, 2017 at 8:24 PM, Indunil Upeksha Rathnayake <
> indu...@wso2.com> wrote:
>
>> Hi,
>>
>> With IS 5.3.0, we have currently provided a Rest API for resending
>> confirmation code
Hi Youcef,
Setting the library parameter is not possible with the current
implementation. A git issue[1] is created for this and will look into
adding this feature.
Thanks,
Viduranga.
[1] https://github.com/wso2/carbon-apimgt/issues/4786
On Mon, Dec 4, 2017 at 12:29 PM, Youcef HILEM
Hi Indunil/Isura,
I have a general comment on this. Are we not planning to support this in
the UI at least in the public release? Because planning for backend only
IMO is not a good idea from previous experience because it will remain at
the same state for years. Don't want to go back there. And
Hi Tharindu,
+1 to keep the scopes in the Swagger definition.
When we generate SDKs for APIs in APIM, swagger codegen generates
authentication procedures (Sample code + documentation) for the SDK only if
there are security scopes in the swagger definition. This issue is there is
API-M 210,
On Mon, Dec 4, 2017 at 6:54 AM, Indunil Upeksha Rathnayake wrote:
> Hi,
>
> With IS 5.3.0, we have currently provided a Rest API for resending
> confirmation code (Refer [1]), which supports only for self signup feature.
> So that, we are planning to provide a more generic
Tharindu,
IMO, we should extend key-manager interface for this implementation,
because there could be instances where, some key managers does not support
resource registrations OOB.
+1 for keep scopes in swagger.
Regards
Roshan.
On Tue, Dec 5, 2017 at 7:15 AM, Tharindu Dharmarathna
Hi All,
We are going to develop Resource Registration Rest API for engaging Scope
for the resource. I had come up with below flow in order to do the above.
In Above Diagram for Store Scopes, we can do below two ways.
1. Store under swagger.json as security definition
2. Store In
Hi,
With IS 5.3.0, we have currently provided a Rest API for resending
confirmation code (Refer [1]), which supports only for self signup feature.
So that, we are planning to provide a more generic REST API and a OSGi
service, for resending confirmation code for any scenario.
Following are the
Hi All,
We released the Google Pub/Sub connector with the above methods. please
find it in the store [1].
[1]
https://store.wso2.com/store/assets/esbconnector/details/965e5fd9-8a43-424b-a69f-bc1f1af5eb12
Thank you.
Regards,
Janani Thangavel
Associate Software Engineer
WSO2 Inc :
+1 Chamila for both #1 and #2.
Thanks
Cyril
Le 4 déc. 2017 7:42 AM, "Chamila De Alwis" a écrit :
IMO image size can be a concern, especially with C4 servers. Users who are
used to work with image sizes around 500-600MB would be in for a surprise
if we rack up an image to a
15 matches
Mail list logo