I would like to add more parameter to the mail template.
I only found existing mail template parameter in this doc :
http://tharindue.blogspot.fr/2016/01/self-sign-up-for-user-accounts-with.html
which are :
{first-name}
{confirmation-code}
{userstore-domain}
{user-name}
{tenant-domain}
These parameters should definitely be in WSO2IS doc.
Are there more parameters in the version 5.2 or 5.3 ?
I would like to have :
{last-name}, {user-id} and also claims values
Should I create a JIRA issue ?
Regards
Supporting all the user claims at email templates is done for the upcoming IS 5.3.0 release. You can refer the JIRA here for more information. You can also checkout the latest milestone builds from here if you are interested.
You should be able to write a custom email notification sender. Found this on google. Have a look.
Related
I've created a custom template for B2C Sign In User flow. I wanted to add instruction text on the top of the page in 2 languages, so I created 2 templates, uploaded them to folders in blob storage.
When I insert a link to the User flow it is working for separated languages, but once I add a wildcard value {Culture:RFC5646} (which is recommended on MS docs) it doesn't work.
Have you got any ideas or advices of how this needs to be done?
Just to add another issue to this: the language is custom.
Thanks!
The language customization feature allows Azure AD B2C to pass the OpenID Connect parameter ui_locales to your endpoint. Your content server can use this parameter to provide language-specific HTML pages. The important thing is that the parameters must be passed in here.
Reference : azure b2c - custom UI - localize custom label
I managed to find the answer.
Instead of {Culture:RFC5646} I've added {Culture:LanguageName} and it fixed the issue!
Link below:
Question about Culture:RFC5646 and ContentDefinitions
According to WSO2 documentation (https://docs.wso2.com/display/IS570/Username+Recovery) we can add additional attributes to the Username Recovery. I have selected an attribute and it displays on the Username Recovery form, but it does not appear to be used in the search filter to find the account.
The only field that it appears to use properly is email. Unfortunately, I need to include an additional attribute to distinguish between accounts.
What am I missing to get this to work?
If you are using a WSO2 identity server 5.7, it is a reported issue. It has been fixed in IS-5.9 onwards. You can patch the fix by applying the changes in 2, to get it to work in IS-5.7
1 -https://github.com/wso2/product-is/issues/6158
2 -https://github.com/wso2/carbon-identity-framework/pull/2380
As mentioned in the title I need to get Ticket's TimeUnit via OTRS soap service (v 3.3). It is standard field used in create Ticket service.
The problem is that GetTicket service receives all the expected fields but TimeUnit.
Ok, as I have explored OTRS docs and all the stuff I see that standard open source version of OTRS does not support getting TimeUnit field with GetTicket operation (in GenericInterface).
The only way is to add the functionality by developing source code of GenericInterface or by adding external OTRS plugin (if exists).
It is not a configuration matter.
I am trying to perform a search via the Facebook API and getting the following error from Facebook - (#11) Post search has been deprecated
URL I am using to query graph:
https://graph.facebook.com/search?q=search_query&type=post&access_token={access_token}
Any ideas why this is happening as I can't seem to find anything about the post search being deprecated?
UPDATE
Graph API v1.0 has been fully deprecated and is no longer available as a workaround. Original answer below for reference.
Yes, version 2.0 of the GraphAPI does not let you search for posts anymore. See the updated documentation.
You can continue to search for posts by changing your API call to:
https://graph.facebook.com/v1.0/search?q=search_query&type=post&access_token={access_token}
I.e. add v1.0/ after https://graph.facebook.com/
As mentioned Niraj Shah, searching by the type "post" is already 'Legacy' API method and could be used with path '/v1.0/search?type=post', BUT there is one more trouble - your application can't use v1.0 API, if it was created after 30th April 2014. So be careful. According this answer.
According to Facebook, "All Facebook-enabled apps will be automatically upgraded to API v2.0 on April 30, 2015. If you have mobile apps, you'll need to update your app well before that date - leaving additional weeks for people to download your update from the store", and "Public post search is no longer available".
Check this for details: https://developers.facebook.com/docs/apps/upgrading
I have been having this problem since i upgraded my sites from Magento 1.3 - Magento 1.6 .
When a customer requests a new password using the Forgotten Password field they recieve an email however the new password comes through as blank.
Dear, ****,
Your new password is:
You can change your password at any time by logging into your account.
Thank you again.
I have read alot of different fixes all similaring the fact that the customer.xml may be out of date, I have tryed alot of fixes and none seem to work. Any help on the topic would be much appreciated.
Thank You in advance
I've had this happen before. In my case it was because a customised template had been created, and in the newer version of Magento it changes how this process works slightly. Previously a new password was generated and sent plain text. In newer version it simply sends a link which you can follow to manually specify your new password (which in my opinion is much better functionality). Check which template it used here...
System > Configuration > Customer > Customer Configuration > Password Options > Forgot Email Template
If it is not the default template then go to System > Transactional Emails and generate a new forgot password e-mail and either modify as needed then change this to be the used e-mail (via the configuration mentioned previously). Or perhaps easier, copy the main content (echo'ing of the link) into your current template.