Re: [Dev] CORS error in public server

2018-08-03 Thread shibsankar 
any comments to this please ?

Regards
Shib

On Thu, Aug 2, 2018 at 1:45 PM, shibsankar  wrote:

>
> It works when I whitelist localhost in wso2 api manager XML  and run from
> local.
>
> But when I move the application to a public server and whitelist the
> public IP in wso2 api manager XML , it does not work.
>
> My CORS configuration Is correct as per your link.
>
> Issue is when I move my angular application to public server and whitelist
> the public server IP in wso2 api manager XML it throws error.
>
>
> Please see the earlier screenshot for error message and IP white listing.
>
> Regards
> Shib
>
>
> On Wednesday, August 1, 2018, Rukshan Premathunga 
> wrote:
>
>> Hi Shib,
>>
>> It seems like you have try to do a request to token api. CORS
>> configuration done in the api-manager.xml not added to the token api by
>> default and you have to do some changes to make it work.
>> Please refer following article which explain how to enable cors for token
>> api.
>>
>> [1] https://medium.com/@iloshinikarunarathne/enabling-cors-
>> for-token-apis-in-wso2-apim-d04f7ef5171
>>
>> Thanks and Regards
>>
>> On Wed, Aug 1, 2018 at 9:22 PM, shibsankar  wrote:
>>
>>> any comments on this, please?
>>>
>>> Regards
>>> Shib
>>>
>>>
>>> On Tue, Jul 31, 2018 at 11:31 AM, shibsankar  wrote:
>>>
 any comments on this?

 Regards
 Shib


 On Mon, Jul 30, 2018 at 12:15 PM, shibsankar  wrote:

> Hi
>
> I have deployed my angular application in a  *public server. *
>
> and then *whitelisted  the public server IP* in wso2's
> *api-manager.xml *
>
>
>
> However, when I call  wso2  token API  from my angular application I
> am getting CORS error.
>
> *Please see the CORS error and WSO2 settings in the screenshot
> attached.*
>
> Could you please suggest what is wrong here and how to fix it?
>
> Regards
> Shib
>
>
>
>
>


>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Rukshan Chathuranga.
>> Software Engineer.
>> WSO2, Inc.
>> +94711822074
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] IAM: Signature validation failed error

2018-08-03 Thread Tharindu Edirisinghe 
Hi Achini,

If you are trying this flow just for testing purpose, a quick solution is
to turn off signature validation in SAML response and assertion using
following two properties in the SAML2SSOAuthenticator configuration in
authenticators.xml file.

false
false

By default above are commented out.

If you need to enable the response and assertion signature validation and
get it to working, then set the above two properties to true and add the
following property as well.

wso2carbon

Here you need to give the certificate alias of the public certificate of
the signing entity, which should be IS itself in this case. (If it is a
different entity, then we need to import the certificate to the
wso2carbon.jks with some alias and provide that alias in above property.

Thanks,
TharinduE

On Thu, Aug 2, 2018 at 7:25 AM Achini Jayasena  wrote:

> Hi All,
>
> Signature validation failed, occurred in following scenario.
>
> *Scenario:* IAM it self enable multi factor authentication (scenario 05)
> and sp creation from metadata url configurations.
>
> *Test steps:*
> Step 01: Create user
> Step 02: Create IDP (twitter)
> Step 03: Create SP for carbon server from metadata file url configurations
> (please find the metadata file attached here with)
> Step 04: Update Sp for enable MFA
>
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/; 
> xmlns:xsd="http://org.apache.axis2/xsd; 
> xmlns:xsd1="http://model.common.application.identity.carbon.wso2.org/xsd;>
>
>
>   
>  
>  
> 
> ${appID}
> ${spname}
> ${spdescription}
> 
>
>   ${carbonServer}
>   samlsso
>   standardAPP
>   
>  false
>  
>  
>  
>  0
>  attrConsumServiceIndex
>  false
>  
>  ${serviceIndex}
>   
>
>
>   
>   ${carbonServer}
>   openid
>   standardAPP
>
>
>   
>   ${carbonServer}
>   passivests
>   standardAPP
>
> 
> 
>false
>
> 
> /** Configure Multi Steps */
> 
>
>
> false
>
>
>   
>   true
>   true
>   
>   
>   
>  
>  basic
>  
>  false
>  
>  BasicAuthenticator
>  
>  
>  true
>   
>   
>   1
>   
>
>
>   
>   false
>   false
>   
>   
>  
> 
> 
> 
> ${idpname}
> false
> TwitterAuthenticator
> true
>  
>  
>  
> ${idpname}
> false
> TwitterAuthenticator
> true
>  
>  
>  
> ${idpname}
>  false
>  false
>  false
>   
>   
>   2
>   
>
>
>flow
>id
> 
> 
>
> 
> 
>
> 
> false
>  
>   
>
>
> Step 04: Change /repository/conf/security/authenticators.xml
> file,  following tags as below.
>  
> 1
> Step 05:Restart the carbon server
> Step 06: Do basic authenticate
> Step 07: Do twitter authenticate
>
> *Expected result:*
> Navigate to the IS home
>
> *Actual result:*
>
> Error log:
>
> [2018-08-02 06:35:45,738]  WARN
> {org.wso2.carbon.identity.application.authentication.framework.handler.claims.impl.DefaultClaimHandler}
> -  Subject claim could not be found amongst service provider mapped
> unfiltered local claims
> [2018-08-02 06:35:45,739]  WARN
> {org.wso2.carbon.identity.application.authentication.framework.handler.sequence.impl.DefaultStepBasedSequenceHandler}
> -  Subject claim could not be found. Defaulting to Name Identifier.
> [2018-08-02 06:35:49,612]

[Dev] WSO2 Identity Server 5.7.0-alpha Released!

2018-08-03 Thread Senthalan Kanagalingam 
WSO2 Identity and Access Management team is pleased to announce the release
of Identity Server 5.7.0 Alpha!
Download

You can download WSO2 Identity Server 5.7.0 alpha from here

.

You can download WSO2 Identity Server Analytics 5.7.0 alpha from here

.
How to run

   1.

   Extract the downloaded zip file.
   2.

   Go to the bin directory in the extracted folder.
   3.

   Run the wso2server.sh file if you are on a Linux/Mac OS or run the
   wso2server.bat file if you are on a Windows OS.
   4.

   Optionally, if you need to start the OSGi console with the server, use
   the -DosgiConsole property when starting the server.

What's new in WSO2 Identity Server 5.7.0 Alpha

   -

   Adaptive authentication
    provides
   the ability to dynamically change the authentication flow depending on user
   attributes, request attributes, and analytics decisions.


A list of all the new features and bug fixes shipped with this release can
be found here 
Known Issues

All the open issues pertaining to WSO2 Identity Server are reported at the
following location:

   -

   IS Runtime 
   -

   IS Analytics 

Contribute to WSO2 Identity ServerMailing Lists

Join our mailing lists and correspond with the developers directly. We also
encourage you to take part in discussions related to the product in the
architecture mailing list. If you have any questions regarding the product
you can use our StackOverflow forum to raise them as well.

   -

   Developer List: dev@wso2.org
   -

   Architecture List: architect...@wso2.org
   -

   User Forum: StackOverflow
   

Reporting Issues

We encourage you to report issues, improvements, and feature requests
regarding WSO2 Identity Server through our public WSO2 Identity Server GIT
Issues .

For more information about WSO2 Identity Server, please see
https://wso2.com/identity-and-access-management or visit the WSO2 Oxygen
Tank  developer portal for additional resources.


~ The WSO2 Identity and Access Management Team ~
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] BPMN-Explorer can not accessible for tenant

2018-08-03 Thread Vinod Kavinda 
Hi Kavitha,
Did that solved all the issues you encountered?
Just curious!

/Vinod

On Fri, Aug 3, 2018 at 2:08 PM Kavitha Subramaniyam 
wrote:

> Hi,
>
> This issue occurred because the bpmn-explorer has been copied to '
> business-process/repository/deployment/server/jaggeryapps/' after tenant
> modification, according to doc description in [1].
> But it should be copied to '
> business-process/repository/tenants//jaggeryapps/' instead.
>
> Thanks Milinda to find this.
>
> @Praneesha, please update the doc[1] accordingly?
>
> [1] https://docs.wso2.com/display/EI610/Using+the+BPMN+Explorer
>
>
>
>
> On Fri, Aug 3, 2018 at 1:34 PM, Milinda Perera  wrote:
>
>> Hi Kavitha
>>
>> On Fri, Aug 3, 2018 at 11:57 AM, Kavitha Subramaniyam 
>> wrote:
>>
>>> Hi Vinod/Milinda,
>>>
>>> For the login issue, please check whether the user "kavi...@test.com"
 has the login permission.

>>> Issue I faced is, accessing tenant's bpmn explorer is not working after
>>> done configurations.
>>> URL : https://localhost:9445/t/test.com/jaggeryapps/bpmn-explorer/
>>>
>>>
>>> Note that I need to test for tenant admin user, so I believe no need to
>>> update the permissions for tenant admin like as super admin user can log in.
>>>
>>
>> Do you see any error logs in the console?
>>
>> Thanks,
>> Milinda
>>
>> --
>> Milinda Perera
>> Senior Software Engineer;
>> WSO2 Inc. http://wso2.com ,
>> Mobile: (+94) 714 115 032
>>
>>
>

-- 
Vinod Kavinda
Senior Software Engineer
*WSO2 Inc. - lean . enterprise . middleware .*
Mobile : +94 (0) 712 415544 
Blog : http://soatechflicks.blogspot.com/
[image: http://wso2.com/signature]

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

Re: [Dev] BPMN-Explorer can not accessible for tenant

2018-08-03 Thread Kavitha Subramaniyam 
Hi,

This issue occurred because the bpmn-explorer has been copied to '
business-process/repository/deployment/server/jaggeryapps/' after tenant
modification, according to doc description in [1].
But it should be copied to '
business-process/repository/tenants//jaggeryapps/' instead.

Thanks Milinda to find this.

@Praneesha, please update the doc[1] accordingly?

[1] https://docs.wso2.com/display/EI610/Using+the+BPMN+Explorer




On Fri, Aug 3, 2018 at 1:34 PM, Milinda Perera  wrote:

> Hi Kavitha
>
> On Fri, Aug 3, 2018 at 11:57 AM, Kavitha Subramaniyam 
> wrote:
>
>> Hi Vinod/Milinda,
>>
>> For the login issue, please check whether the user "kavi...@test.com"
>>> has the login permission.
>>>
>> Issue I faced is, accessing tenant's bpmn explorer is not working after
>> done configurations.
>> URL : https://localhost:9445/t/test.com/jaggeryapps/bpmn-explorer/
>>
>>
>> Note that I need to test for tenant admin user, so I believe no need to
>> update the permissions for tenant admin like as super admin user can log in.
>>
>
> Do you see any error logs in the console?
>
> Thanks,
> Milinda
>
> --
> Milinda Perera
> Senior Software Engineer;
> WSO2 Inc. http://wso2.com ,
> Mobile: (+94) 714 115 032
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] BPMN-Explorer can not accessible for tenant

2018-08-03 Thread Milinda Perera 
Hi Kavitha

On Fri, Aug 3, 2018 at 11:57 AM, Kavitha Subramaniyam 
wrote:

> Hi Vinod/Milinda,
>
> For the login issue, please check whether the user "kavi...@test.com" has
>> the login permission.
>>
> Issue I faced is, accessing tenant's bpmn explorer is not working after
> done configurations.
> URL : https://localhost:9445/t/test.com/jaggeryapps/bpmn-explorer/
>
>
> Note that I need to test for tenant admin user, so I believe no need to
> update the permissions for tenant admin like as super admin user can log in.
>

Do you see any error logs in the console?

Thanks,
Milinda

-- 
Milinda Perera
Senior Software Engineer;
WSO2 Inc. http://wso2.com ,
Mobile: (+94) 714 115 032
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev