Re: [Dev] Subscription approval task

[Shazni Nazeer]

I think the role that is specified in the SubscriptionsApprovalTasks.ht
below is able to view it.

 

approverRole




What specific permissions in the permission tree that this approver role
should possess in order to approve subscriptions?

On Wed, Jul 18, 2018 at 9:44 AM Shazni Nazeer  wrote:

> I have a subscription creation workflow  configured as below in the
> /_system/governance/apimgt/applicationdata/workflow-extensions.xml
>
>
> http://localhost:9765/services/SubscriptionApprovalWorkFlowProcess/ Property>
>  admin_user
>  admin_password
>  
> https://localhost:8243/services/WorkflowCallbackService
> 
>
> This configuration successfully works and makes the subscription on hold
> when a user subscribes to an API. Is the subscription approval could only
> be done by the admin_user as configured in this? I could only see the
> Approval Tasks for subscription creation if I only log in with the
> admin_user to the admin portal. If I log in with another user account who
> has all the admin permissions, approval tasks don't show up in there.
>
> Is there a way to make this show up for all the admin users? Or better if
> we have another specific role with only approval permission and allow all
> the users on that role to view and approve. Is there a way to achieve this?
>
> Appreciate your feedback
>
> regards
> --
> Shazni Nazeer
>
> Mob : +94 37331
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>
> Blogs :
>
> https://medium.com/@mshazninazeer
> http://shazninazeer.blogspot.com
>
> 
>


-- 
Shazni Nazeer

Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer

Blogs :

https://medium.com/@mshazninazeer
http://shazninazeer.blogspot.com


___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Subscription approval task

[Shazni Nazeer]

I have a subscription creation workflow  configured as below in the
/_system/governance/apimgt/applicationdata/workflow-extensions.xml

   
http://localhost:9765/services/SubscriptionApprovalWorkFlowProcess/
 admin_user
 admin_password
 
https://localhost:8243/services/WorkflowCallbackService


This configuration successfully works and makes the subscription on hold
when a user subscribes to an API. Is the subscription approval could only
be done by the admin_user as configured in this? I could only see the
Approval Tasks for subscription creation if I only log in with the
admin_user to the admin portal. If I log in with another user account who
has all the admin permissions, approval tasks don't show up in there.

Is there a way to make this show up for all the admin users? Or better if
we have another specific role with only approval permission and allow all
the users on that role to view and approve. Is there a way to achieve this?

Appreciate your feedback

regards
-- 
Shazni Nazeer

Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer

Blogs :

https://medium.com/@mshazninazeer
http://shazninazeer.blogspot.com


___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Committers += Chiran Fernando

[Tishan Dahanayakage]

Hi all,

It's my pleasure to announce Chiran Fernando as a WSO2 Committer. He has
been a valuable contributor to WSO2 Analytics team.

Congratulations Chiran and keep up the good work!!.

Thanks,
/Tishan

-- 
Tishan Dahanayakage
Associate Technical Lead
WSO2, Inc.
Mobile:+94 716481328

Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
re-transmit, disseminate, or otherwise use the information contained in
this communication. Internet communications cannot be guaranteed to be
timely, secure, error or virus-free. The sender does not accept liability
for any errors or omissions.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] CORS ERROR in Custom Service API

[Dushani Wellappili]

Hi Shib,

Sorry for the late response.

After you type the value 'http://localhost' in 'Access Control Allow
*Origins' *text box, you need to press Enter key to add that value to the
text box.

Could you please try that and see.

Regards,

*Dushani Wellappili*
Software Engineer - WSO2

Email : dusha...@wso2.com
Mobile : +94779367571
Web : https://wso2.com/




On Wed, Jul 18, 2018 at 5:43 PM shibsankar  wrote:

> Any comments to this?
>
> Regards
> Shib
>
> On Mon, Jul 16, 2018 at 1:34 PM, shibsankar  wrote:
>
>> Yes.  I was asking configuring CROSS-ORIGIN resources sharing for a
>> particular API.
>>
>>
>> I checked your link and I  did the configuration for
>> Access-Control-Allow-Origin as value  http://localhost but this value is
>> not saved.
>>
>> Why this value is not saved ?
>>
>> Please find the screenshots attached to before saving and after saving of
>> CORS configuration.
>>
>> Is there anything I'm missing?
>>
>>
>> Regards
>> Shib
>>
>>
>> On Fri, Jul 13, 2018 at 10:18 PM, Dushani Wellappili 
>> wrote:
>>
>>> Those API based CORS configurations are set as properties
>>> in CORSRequestHandler of the particular API. You can see that in your
>>> relevant api.xml file which inside the
>>> synapse-configs/default/api directory.
>>>
>>>
>>> Regards,
>>>
>>> *Dushani Wellappili*
>>> Software Engineer - WSO2
>>>
>>> Email : dusha...@wso2.com
>>> Mobile : +94779367571
>>> Web : https://wso2.com/
>>>
>>>
>>>
>>>
>>> On Fri, Jul 13, 2018 at 10:09 PM Dushani Wellappili 
>>> wrote:
>>>
 Hi Shib,

 If I have understood correctly, you are asking about configuring
 Cross-Origin Resource Sharing for a particular API. Please refer this [1]
 documentation for enabling API based CORS configurations and see whether it
 works for you.


 [1]
 https://docs.wso2.com/display/AM200/Enabling+CORS+for+APIs#EnablingCORSforAPIs-EnablingCORSPerAPI

 Thanks.

 Regards,
 Dushani Wellappili
 Software Engineer - WSO2

 Email : dusha...@wso2.com
 Mobile : +94779367571
 Web : https://wso2.com/



 *Dushani Wellappili*
 Software Engineer - WSO2

 Email : dusha...@wso2.com
 Mobile : +94779367571
 Web : https://wso2.com/




 On Fri, Jul 13, 2018 at 4:46 PM shibsankar  wrote:

> Hi ,
>
> I'm  getting  CORS  ERROR  in  my OrderWorkFlow service API
> invocation.
>
>
> Which  *file / **files*  has the  CORS configuration in WSO2  for   
> *Custom
> Service  **API*  ?
>
>
> *Error :*
>
> Failed to load 
> *http://xx-xx-xxx-xx-xx..xx.xxx.xxx:8280/bsi/custOrderWorkflow/v1/init
> :
> The value of the 'Access-Control-Allow-Origin' header in the response must
> not be the wildcard '*' when the request's credentials mode is 'include'.
> Origin 'http://localhost ' is therefore not allowed
> access. The credentials mode of requests initiated by the XMLHttpRequest 
> is
> controlled by the withCredentials attribute.*
>
> Regards
> Shib
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>

>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] CORS ERROR in Custom Service API

[shibsankar]

Any comments to this?

Regards
Shib

On Mon, Jul 16, 2018 at 1:34 PM, shibsankar  wrote:

> Yes.  I was asking configuring CROSS-ORIGIN resources sharing for a
> particular API.
>
>
> I checked your link and I  did the configuration for
> Access-Control-Allow-Origin as value  http://localhost but this value is
> not saved.
>
> Why this value is not saved ?
>
> Please find the screenshots attached to before saving and after saving of
> CORS configuration.
>
> Is there anything I'm missing?
>
>
> Regards
> Shib
>
>
> On Fri, Jul 13, 2018 at 10:18 PM, Dushani Wellappili 
> wrote:
>
>> Those API based CORS configurations are set as properties
>> in CORSRequestHandler of the particular API. You can see that in your
>> relevant api.xml file which inside the synapse-configs/default/api di
>> rectory.
>>
>>
>> Regards,
>>
>> *Dushani Wellappili*
>> Software Engineer - WSO2
>>
>> Email : dusha...@wso2.com
>> Mobile : +94779367571
>> Web : https://wso2.com/
>>
>>
>>
>>
>> On Fri, Jul 13, 2018 at 10:09 PM Dushani Wellappili 
>> wrote:
>>
>>> Hi Shib,
>>>
>>> If I have understood correctly, you are asking about configuring
>>> Cross-Origin Resource Sharing for a particular API. Please refer this [1]
>>> documentation for enabling API based CORS configurations and see whether it
>>> works for you.
>>>
>>>
>>> [1] https://docs.wso2.com/display/AM200/Enabling+CORS+for+APIs#E
>>> nablingCORSforAPIs-EnablingCORSPerAPI
>>>
>>> Thanks.
>>>
>>> Regards,
>>> Dushani Wellappili
>>> Software Engineer - WSO2
>>>
>>> Email : dusha...@wso2.com
>>> Mobile : +94779367571
>>> Web : https://wso2.com/
>>>
>>>
>>>
>>> *Dushani Wellappili*
>>> Software Engineer - WSO2
>>>
>>> Email : dusha...@wso2.com
>>> Mobile : +94779367571
>>> Web : https://wso2.com/
>>>
>>>
>>>
>>>
>>> On Fri, Jul 13, 2018 at 4:46 PM shibsankar  wrote:
>>>
 Hi ,

 I'm  getting  CORS  ERROR  in  my OrderWorkFlow service API  invocation.


 Which  *file / **files*  has the  CORS configuration in WSO2  for   *Custom
 Service  **API*  ?


 *Error :*

 Failed to load 
 *http://xx-xx-xxx-xx-xx..xx.xxx.xxx:8280/bsi/custOrderWorkflow/v1/init
 :
 The value of the 'Access-Control-Allow-Origin' header in the response must
 not be the wildcard '*' when the request's credentials mode is 'include'.
 Origin 'http://localhost ' is therefore not allowed
 access. The credentials mode of requests initiated by the XMLHttpRequest is
 controlled by the withCredentials attribute.*

 Regards
 Shib
 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev

>>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IAM] Configuring Different Federated Identity Providers for My Enterprise Customers

[Johann Nallathamby]

Hi IAM Team,

Following is the use case I want to accomplish. But I am not able to figure
out how I would be able to do it.

I have IS running with multiple tenants. Each tenant is an enterprise
customer of mine. I have a SaaS application registered in super tenant that
all my customers can access. Currently all my customers can login to this
application using their credentials registered in IS.

What I want be able to do now is, federate the logins to my customer's
on-premise identity provider, so that I don't have to manage separate
passwords for them and the customers' users can use their enterprise
credentials to access my application as well.

*Condition:* Some customers may still want to continue using IS's
credential store, while some other customers may want to integrate their
on-premise identity providers.

How could I accomplish this scenario?

Thanks & Regards,
Johann.

-- 

*Johann Dilantha Nallathamby*
Senior Lead Solutions Engineer
WSO2, Inc.
lean.enterprise.middleware

Mobile: *+94 77 7776950*
LinkedIn: *http://www.linkedin.com/in/johann-nallathamby
*
Medium: *https://medium.com/@johann_nallathamby
*
Twitter: *@dj_nallaa*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev