I need to implement user verification using email containing OTP(Randomly generated 4 digit number) for newly registered user accounts in WSO2 Identity Server but I could not find such functionality. Is there any feature in the repository that might help me?
You can follows the https://docs.wso2.com/display/ISCONNECTORS/Configuring+EmailOTP+Authenticator it describes the steps that you need to follow
Related
I want to use Google Authenticator for 2-factor authentication with WSO2 identity server 5.7.0. The Google Authenticator should provide a One-Time Password which is valid only for a very short duration. Using the email id, password and OTP (generated from Google Authenticator) a user should be allowed to sign in into an application.
I cannot find how to implement google authenticator in the link mentioned below WSO2 Identity Server Authenticators and Connectors Documentation
Can anyone provide some steps in the direction to implement Google Authenticator with WSO2?
Note: I am not referring to using Google as a federated authenticator.
As for me for your use case you don't need google authenticator you need email otp[1]. You can configure your email otp to generate from google. You can enable it as a second factor in authentication. So the first user will login using user name and password then user will be asked for the otp that generated from google. That will be sent to the user email account.
If you want to use the google authenticator to get the otp not the email then you should use wso2 totp. [2]
[1]. https://docs.wso2.com/display/IS570/Configuring+Email+OTP
[2].https://docs.wso2.com/display/ISCONNECTORS/Configuring+TOTP+Authenticator
Hi i Want in API manager WSO2 in store section after user registered Send email with link to confirm account
am version: 2.5.0
Please Help Me
Your requirement can be achieved through a custom workflow extension. By default there is a custom workflow to the user signup process. You may need to extend that to send an email. Please refer to this.
Suggest me some process which i follow to complete my task. I am new in using wso2.
1) How the user will able to login in their application either using facebook account or google account or wso2 account using wso2 identity server.
2) And there is one more condition some user login based on resources(link buildings).
for that resource user will able to login with single sign on using wso2 identity server.
Step 01: You can setup federated authentication as per [1]. Do it for both Facebook and Google.
Step 02: Configure multiple options from advance authentication configuration. Once you complete Step 01 pls get back to explain Step 02.
[1] https://docs.wso2.com/display/IS570/Configuring+Federated+Authentication
We managed to lock the user store account after self registering an account in the store, but the only way we figured it out to unlock the account is using the admin console (CARBON). We've been trying to make the confirmation e-mail work after self sign up, but we had no luck until now. How could we achieve that?
We are using the WSO2 API Manager 2.5.0. Community Edition.
I am also stopped in this point.
I only see how to configure this on WSO2 Identity Server, here.
But how can I do the same in WSO2 API Manager?
I guess using workflows, or maybe through platform configuration, but it is not explained anywere.
Same question is asked also here
It is reported as bug here
Could someone bring light this issue?
This is possible with the use of user signup workflow in APIM [1]. As explains in [2], you can send an email when a user sign up request comes or when a user sign up request completes.
https://docs.wso2.com/display/AM260/Adding+a+User+Signup+Workflow
https://docs.wso2.com/display/AM260/Customizing+a+Workflow+Extension
I'm using WSO2 Identity Server 5.0 for SAML SSO and need to have user passwords expire after n days. I found the following properties in identity-mgt.properties but I can't find any documentation on how to use them. Is this functionality implemented/available?
Authentication.Policy.Check.Password.Expire=false
Authentication.Policy.Password.Expire.Time=0
Thanks
These two properties had been introduced initially to IS planning to support password expiry, but the implementation was never done.
if Authentication.Policy.Check.Password.Expire is set to true, then the when the user updates the password, timestamp of password update is set as a user claim.
But Authentication.Policy.Password.Expire.Time is not logically used anywhere in the code base, and ideally should be removed.
Anyways, you can achieve the same functionality in a different way using password policy authenticators in IS. Hope this helps.