When I send the enroll invitation email to the user I got issue please refer the [Image1 & Image1] screen shot for your reference.
And also please find the below linkView the doc which I have referred to setup Email configuration in EMM.
Version I have tested in 2.1.1 and 2.2.0 Beta
Image1
Image2
This issue is probably due to misconfiguration of email template configuration located at "/repository/resources/email-templates" directory. It looks like you have accidentally changed the xml element.
Thanks,
I have analyzed above question in Stackoverflow.6 months ago someone already discussed regarding the email issue - Setting Up Email Notification For Wso2EMM Please refer the link, As per their discussion the email issue is already in WSO2 EMM 2.0.1 version. I also checked in latest 2.1.1 versions I have faced the same issue. Is it will be fixed in upcoming version 2.2.0? WSO2 Team awaiting for your response.
Related
I am implementing push notifications from my server to the users who are subscribed to my server.
Right now sending the push notifications to Firefox users works like a charm. However, on Chrome I get an Unauthorized Registration error. I am using Django as a backend.
In this image are the relevant parts of the error and my code (email edited), aswell as the subscription. If any more information is needed please let me know.
Does anyone know why I can't send push notifications on Chrome?
And I am using this library.
In the murky depths of Google and Github I have found the answer. If you install pywebpush it installs v1.2.2 of py-vapid, which had a bug in it. Overwriting this package with
pip install py-vapid --upgrade
installs the patched version 1.2.3 (released only 5 days ago as of this post), fixes the Unauthorized bug I was having.
I've just pushed pywebpush 1.0.2 which includes py-vapid 1.2.3. Sorry for the delay, but it was unavoidable.
Please don't be afraid to file issues against the package. I do try to respond fairly quickly and it helps out everyone.
Since I already know APIM 1.9.0 is default support BAM, that UI is for deploy the BAM analytics artifacts called toolbox. When you work with DAS, you should leave Data Analyzer Configurations as blank. And need to deploy artifacts(CaPP) manually on DAS .
I seached and found below link which might be helpful:
http://blog.rukspot.com/2015/09/publishing-apim-runtime-statistics-to.html
But the bad thing is for unknown reason I tried times to access this link ,,all failed.
Can anybody help to paste the content of above link here or just send a private mail to me via my mail : menglong567#aliyun.com
That would be very appreaciated !
Please find the official documentation for WSO2 API-M 1.9.0 statistics configurations in here.
All the necessary information is covered in the official doc.
We have recently received two alerts regarding our facebook app.
Your app is still calling Graph API v1.0 which will be
deprecated on April 30, 2015. You must upgrade this app to v2.0 or
greater before that date.
To help you experience the potential effects of this migration,
starting tomorrow at 12pm PST, the admins, developers, testers and
Test Users associated with this app will be upgraded to use API v2.0
by default. This change won't affect your public users until April 30,
2015.
You'll be able to temporarily opt-out of this behavior in the
Migrations tab of your app's dashboard - but the migration will be
automatically re-enabled every two weeks until April 30, 2015.
For more information, please read our upgrade guide and login review
guide.
The second one is very similar and starts with:
We have detected that your app is still calling Graph
API v1.0 which will be deprecated on April 30, 2015. You must upgrade
this app to v2.0 or greater before that date.
However, we have been using Graph API v2.2 for serveral months now by specifying api version in koala config (we always use koala to call GraphAPI):
Koala.config.api_version = "v2.2"
Since we need the subscribed_apps endpoint, we are using v2.2. Switching to v1.0 results in OAuthException, code: 12, message: (#12) Requires version v2.2 or higher [HTTP 400] in case of subscribed_app calls.
I know that not specyfing a version at all results in choosing the oldest available one but we have specified the version in koala, so it's not the point in our case.
Is it possible to find out what caused the alert from Facebook?
I have found an answer to my problem and would like to present all the facts.
For older applications you will see a different message, for example that your app upgrade is completed in 98%.
For applications created quite recently (mine was created in July 2014) that are already version v2.0 or higher you might receive an alert but the message you can check at https://developers.facebook.com/apps/upgrade/ says:
You do not need to upgrade any apps.
I also received a piece of advice from Facebook:
If you're confident your app is upgraded, you can go into the
Migrations tab of the Settings section of the App Dashboard - and flip
the "Use Graph API v2.0 by default" switch to "On" - then you can be
sure you're API migration is ready for April 30th.
If you don't see that setting then you're already using v2.0 or
greater, so you have nothing to worry about.
If you are sure that neither your server-side calls nor your client-side logins use version v1.0 or you chose option "Use Graph API v2.0 by default", you can assume that your app is ready for April 30th and ignore the alerts.
Here you can find some information about the bug that probably causes these alerts: https://developers.facebook.com/bugs/957020271005002/. This issue won't be fixed.
We are using WSO2 4.1.1 for user management. Is there a way to do a session time out in WSO2 4.1.1?
(I am looking if there is a fix for this in WSO2 4.1.1. Currently, I am not looking at migrating to WSO2 4.5
where this is mentioned as a supported feature).
I am referring to the following link where it says the WSO2 4.1.1.code has been changed to handle session time out.
https://wso2.org/jira/browse/IDENTITY-1030
Are these changes available as a new version of jar compatible with the WSO2 4.1.1 version?
Thanks in advance for the help
You won't be able to get a new version of the jar and use it with the WSO2 IS 4.1.1. AFAIK, IS 4.1.1 was never released, I think you are using a build shared via dev# list.
Anyway, you can try following.
Checkout the source for the corresponding jars in WSO2 IS 4.1.1. Try to checkout from branch. For example: https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/components/identity/org.wso2.carbon.identity.base/
Fix the issue and do 'mvn clean install'
Copy the target jar as a patch.
Run server with -DapplyPatches
In this way, you can try to fix this issue.
If we discover issues with any product after it has been released, you will be able to get the fix only in a newer version. Otherwise, you need to patch the existing jar versions.
I hope this helps.
I have same question for
Writing a Custom Broker about WSO2 CEP
on The Article of the link, Mr.mohanadarshan answerd https://stackoverflow.com/users/2168723/mohanadarshan
But, I can not understand the link of the pack in the answer of the link article.
And I have no times using this Stack Overflow.
So I has no reputation.
Please answer my question.
Regards,
You need to download the WSO2 Complex Event Processor 2.1.0 product again from the WSO2 web site. This is what referred as the 'pack'. Just click on "Binary" link under "Download" section. Make sure that you do not use any download accelerators when downloading.
I hope this helps.