I am trying to do email verification with mailtrap and laravel. I did it with official laravel documentation https://laravel.com/docs/9.x/verification. I did it step by step except for the two last steps which I currently don't need. I connected my .env with mailtrap and in MAIL_FROM_ADDRESS I used the same email adress as I have setup in mailtrap. I forgot to mention that I have registration and login setup with Auth and I didn't wrote them manually.
But when I tried to register, after filling the information needed in registration and clicking on registrate showed up error Route [verification.verify] not defined. I searched a lot and found this three articles: Verification email not sent for custom route get Route [verification.verify] not defined , https://laracasts.com/discuss/channels/laravel/message-route-verificationverify-not-defined , https://laracasts.com/discuss/channels/laravel/resolve-verificationverify-not-define
I think that the first two solutions should be included in documentation, which I implement and I don't understand the third one. Any suggestions?
Related
I'm trying to implement a custom reset page in Auth0 using their Universal Login system.
I managed to set up the login page, but I'm not able to find any relevant documentation regarding password reset and a specific javascript code to pass the information from my form directly trough their API.
Anyone else faced this issued and found a solution or at least a way to hack it?
From what I know, it's impossible to customize the reset password page for Auth0 - Universal Login. Haven't found a solution after 4 months, searched for solutions every week
we are trying to build an application which is accessable via onetime passwords without a "user" having the need to register.
We did came accross the term magic-links sent via email, but there is only some old experimental keycloack extention for this.
Is there any way to build some auth flow like the following with keycloack?
User A is a fully registered User creating some document. This document needs some interaction with a Third Party Person (TPP) not registered.
Now User A sends an E-Mail invite to the TPP with a link to the document. When the TPP opens the link our application should ask for the email address and send a magic link or code to this email. Whith that email or magic code the user gets access to the document for the time it takes to complete the approval process. After the work of the TTP is done, the access should expire (or expire automatically after X days not used).
It does sound quite similar to what is possible with SaaS offerings like https://magic.link/ or https://www.arengu.com/ but we are using keycloack and would like to integrate it into it as well.
Does anyone have an idea how to achieve this with keycloak?
I know this is outdated, but perhaps someone else coming along may find this useful. There is a newer implementation of this feature provided here: https://github.com/p2-inc/keycloak-magic-link
We have found it usable and useful for our needs and works well in the latest version of Keycloak (18.x).
I'm using Firebase auth to control access to my app and it's been working great and was easy to implement. Now that I'm bringing real testers on, I've got a question.
When a user registers, I'm forcing email verification and that all works fine. I've even found how to somewhat customize the email that user receives asking them to verify their address. However, when the user clicks that link, they get a very generic message:
Your email has been verified
You can now sign in with your new account
Is there any way to customize this? I don't want to do anything particularly fancy - just a more helpful message and maybe a link to return to the app.
Thoughts?
If you mean the web page that they get to when they click the link, there is no way to customize the existing page. But you can create your own page, and host it (for example on Firebase Hosting). For full documentation on this process, see the documentation on creating a custom email action handler.
When i mentioned scope read_all_orders . I faced the following error while installation
Oauth error missing_shopify_permission: read_all_orders
Without read_all_orders scope App install perfectly.
I dont know what happens exactly i am trying both new created store and 2 month old store
My scopes :- 'read_products', 'read_orders', 'read_customers', 'write_orders', 'read_price_rules', 'write_price_rules', 'read_all_orders'
As per Shopify documentation
read_all_orders
Grants access to all orders rather than the default window of 60 days
worth of orders. This OAuth scope is used in conjunction with
read_orders, or write_orders. You need to request this scope from your
Partner Dashboard before adding it to your app.
To do so
read_all_orders access:
From your app's overview page, click App setup.
In the Orders section, click Request access to all orders.
Provide a description about why you are applying for access.
Click Request access.
My app is an approved hidden app in BigCommerce that has all of the scopes selected in the MyApp Technical page. Unfortunately, when I try to oAuth into a user, the following scope 'store_v2_transactions_read_only' returns an 'invalid scope' message. If I take that scope out, the other scopes (for read_only orders, customers, etc.) work fine and I can successfully connect an account using Oauth with my app.
The scope 'store_v2_transactions_read_only' is found in the documentation in the list of scopes here: https://developer.bigcommerce.com/api/#oauth-scopes96. But making the request to connect an account using that scope returns 'invalid_scope' and I can't access user transaction data. Again, all other scopes work, and I have them all selected in the app technical page in the developer portal.
Working in node and using axios to get the token with the oauth code. This list of scopes works:
scope: 'store_v2_customers_read_only store_v2_information_read_only store_v2_orders_read_only store_v2_products_read_only'
The moment I add store_v2_transactions_read_only it returns 'invalid scope', even thought that is the string stated in the docs. It is the same error that shows if I misspell any of the scopes.
Make sure that you're passing in the context in your query string. At the time of writing the API will send back an Invalid scope(s). error seemingly only when you request store_v2_transactions_read_only without this query param. Other scopes seem to work fine, as you've noticed, if this param is not sent.
Can't comment, because I don't have 50 karma, but adding the context to the POST call in postman from the correct answer fixed this issue for me. I had been dealing with it for some time and there isn't a lot of documentation on the BigCommerce side in other forum posts.
I am using the x-www-form-urlencoded params with:
KEY: context
VALUE: stores/abcdefg
The abcdefg is the actual store number/id in the exact format it came in from the callback.