Need Help Deploying Authgear with Specific Email and SMS Providers #4432

ilyas-sudo · 2024-07-06T08:30:45Z

ilyas-sudo
Jul 6, 2024

Hi everyone,

I'm currently setting up Authgear on my server from this documents ( https://docs.authgear.com/deploy-on-your-cloud/local ) and encountering an issue. I've configured it to use Sparkpost for email and SMS Niaga for SMS services. However, I'm getting the following error during startup:

cannot parse app config: invalid configuration: /sms:

I've verified my authgear.yaml configuration, ensuring all necessary fields are correctly filled out. Despite this, the error persists. Could someone please assist me in troubleshooting this issue?

now i have remove the sms and email configration from my authgear.yaml
this is my simple authgear yaml file

root@racknerd-2b1f8ff:/home/myapp# cat authgear.yaml

authenticator:
oob_otp:
sms:
phone_otp_mode: sms
http:
public_origin: http://192.3.239.176:3000
id: my-app
oauth:
clients:
- client_id: 85baaca4cb4809f3
name: Portal
post_logout_redirect_uris:
- http://192.3.239.176:8000/
redirect_uris:
- http://192.3.239.176:8000/oauth-redirect
x_application_type: traditional_webapp
verification:
claims:
email:
enabled: true
required: true

kindly provide me a detailed configration to setup my email and sms provider
Thanks in advance!

pkong-ds · 2024-07-06T11:06:18Z

pkong-ds
Jul 6, 2024

Hi @ilyas-sudo , Thanks for your message.

I noticed your authgear.yaml file has sms as a root-layer field. Meanwhile, it should be /authenticator/oob_otp/sms field. This is likely causing the parsing error you're seeing during startup

// yours
authenticator:
oob_otp:
sms:
// The expected config, referenced from https://docs.authgear.com/deploy-on-your-cloud/configurations/authgear.yaml#annotated-example
# Configure different authenticator behavior.
authenticator:
  oob_otp:
    email:
      maximum: 1
    sms:
      maximum: 1

I would appreciate if you could send your YAML configuration again with by wrapping in triple backticks (```yaml). That way I can help check if your other yaml configuration conform to suggested schema 👍 I suspect your authgear.yaml does not have the correct indentation. Therefore, I highly suggest you to review our documentation on `authgear.yaml` configuration.

Once you've updated your file, try restarting your Authgear server and see if the issue is resolved.

Hope it helps. Let me know if you have any other questions!

0 replies

ilyas-sudo · 2024-07-06T19:45:13Z

ilyas-sudo
Jul 6, 2024
Author

Hi,
Thank you for getting back to me.
I have updated my authgear.yaml configuration with your suggested changes, but I am still encountering the same issue. Here is my updated configuration:

``

authenticator:
  oob_otp:
    email:
      maximum: 1
    sms:
      maximum: 1
http:
  public_origin: http://192.3.239.176:3000
id: my-app
oauth:
  clients:
    - client_id: 85baaca4cb4809f3
      name: Portal
      post_logout_redirect_uris:
        - http://192.3.239.176:8000/
      redirect_uris:
        - http://192.3.239.176:8000/oauth-redirect
      x_application_type: traditional_webapp
verification:
  claims:
    email:
      enabled: true
      required: true
sms:
  default:
    url: https://manage.smsniaga.com/sms/api
##and my credentials


Could you please provide a complete authgear.yaml file with the necessary credentials and configurations for both email and SMS to ensure everything is set up correctly?

Thank you for your assistance.

0 replies

pkong-ds · 2024-07-07T14:14:38Z

pkong-ds
Jul 7, 2024

Hi @ilyas-sudo, thank you for the response.

Similarly, I noticed you have sms as a root-layer field, while it should be verification.claims.phone_number.

# yours
verification:
  claims:
    email:
      enabled: true
      required: true
sms:
  default:
    url: https://manage.smsniaga.com/sms/api
# expected config from https://docs.authgear.com/deploy-on-your-cloud/configurations/authgear.yaml#annotated-example
verification:
  claims:
    email:
      enabled: true
      required: true
    phone_number: # notice this is `phone_number` instead of `sms`, and it is under `verification.claims`
      enabled: true
      required: true

I highly recommend you review our documentation on authgear.yaml. You can utilize browser Find feature by searching keywords like sms, verification, claims.

Let me know if you have other questions!

0 replies

louischan-oursky · 2024-07-08T03:05:43Z

louischan-oursky
Jul 8, 2024
Maintainer

hi @ilyas-sudo . Thanks for reaching out. I guess you want to set up a custom Email provider and a custom SMS provider.

For delivering emails, Authgear supports SMTP, so as long as your provider supports SMTP, you can provide the credentials in authgear.secrets.yaml

For delivering SMS, Authgear natively support Twilio. If you are using a provider other than Twilio, then you need to write a simple HTTP server to work as a bridge between Authgear and your provider.

Here is the example configuration

authgear.yaml

# Only changes are shown here. You keep all your original fields.
messaging:
  sms_provider: custom

authgear.secrets.yaml

# Only changes are shown here. You keep all your original fields.
# secrets is an array. You keep all your original items.
secrets:
# Add this secret to configure SMTP provider
- data:
    # https://developers.sparkpost.com/api/smtp/
    # I assume you are NOT using SparkPost EU.
    # If you do use SparkPost EU, then
    # host: smtp.eu.sparkpostmail.com
    host: smtp.sparkpostmail.com
    port: 587
    username: SMTP_Injection
    password: "REPLACE_YOUR_API_KEY_HERE"
  key: mail.smtp
# Add this secret to configure a custom SMS gateway
- data:
    # The URL to your simple HTTP server that bridges Authgear and your SMS provider.
    # Here I suppose your simple HTTP server serves at /
    url: http://localhost:9876/
    timeout: 10
  key: sms.custom

Then you need to ensure your simple HTTP server run at http://localhost:9876

Here is an example written in Golang

package main

import (
	"fmt"
	"net/http"
	"net/http/httputil"
)

func main() {
	http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
		// Here we just dump the request to see what Authgear gives us.
		// You need to call your SMS provider to deliver SMS in your server!
		b, _ := httputil.DumpRequest(r, true)
		fmt.Printf("%v\n", string(b))
	})
	http.ListenAndServe(":9876", nil)
}

The request you receive from Authgear looks like

POST / HTTP/1.1
Host: localhost:9876
Accept-Encoding: gzip
Content-Length: 106
Content-Type: application/json
User-Agent: Go-http-client/1.1
X-Authgear-Body-Signature: 9597b6b964b39f5590acd0c30f98a548080de8f4759b9a707537e2faac3cbd3f

{"to":"+85251388325","body":"000000 is your Authgear verification code.\n\nDon't share it with anyone.\n"}

You parse the request body as a JSON document. You extract the to field, which is the phone number, and the body field, which is the message to send. Then you check your provider HTTP API and call the corresponding endpoints to actually deliver the SMS message.

0 replies

ilyas-sudo · 2024-07-08T05:50:40Z

ilyas-sudo
Jul 8, 2024
Author

Thank you for response.
i have added your changes to my setup now authgear is running and golang is also running but when i signup the code is not receiving on my gmail

this is my after changes authgear.yaml

authenticator:
  oob_otp:
    sms:
      phone_otp_mode: sms
http:
  public_origin: http://192.3.239.176:3000
id: my-app
oauth:
  clients:
  - client_id: 1babbc19b7e126c8
    name: Portal
    post_logout_redirect_uris:
    - http://portal.192.3.239.176:8000/
    redirect_uris:
    - http://portal.192.3.239.176:8000/oauth-redirect
    x_application_type: traditional_webapp
verification:
  claims:
    email:
      enabled: true
      required: true
messaging:
  sms_provider: custom

and this is my authgear.secret.yaml

secrets:
- data:
    database_schema: public
    database_url: postgres://postgres:postgres@db:5432/postgres?sslmode=disable
  key: db
- data:
    database_schema: public
    database_url: postgres://postgres:postgres@db:5432/postgres?sslmode=disable
  key: audit.db
- data:
    redis_url: redis://redis
  key: redis
- data:
    redis_url: redis://redis/1
  key: analytic.redis
- data:
    host: smtp.sparkpostmail.com
    port: 587
    username: SMTP_Injection
    password: "11aa5c874e7947340a6ad593cd13f7a34505a4e7"
  key: mail.smtp
- data:
    url: http://192.3.239.176:9876/
    timeout: 10
  key: sms.custom

and this is the golang app

package main

import (
        "fmt"
        "net/http"
        "net/http/httputil"
)

func main() {
        http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
                // Dump the request to the console for debugging
                b, _ := httputil.DumpRequest(r, true)
                fmt.Printf("%v\n", string(b))

                // Send a simple HTML response
                w.Header().Set("Content-Type", "text/html")
                fmt.Fprintf(w, "<html><body><h1>SMS Gateway is running</h1></body></html>")
        })

        http.ListenAndServe(":9876", nil)
}

6 replies

ilyas-sudo Jul 9, 2024
Author

I have changed the email credentials and sent the email with the above email.txt file, which was received in the inbox. But the verification code is still not received from authgear

secrets:
- data:
    database_schema: public
    database_url: postgres://postgres:postgres@db:5432/postgres?sslmode=disable
  key: db
- data:
    database_schema: public
    database_url: postgres://postgres:postgres@db:5432/postgres?sslmode=disable
  key: audit.db
- data:
    redis_url: redis://redis
  key: redis
- data:
    redis_url: redis://redis/1
  key: analytic.redis
- data:
    host: mail.erisp.net
    port: 587
    username: [email protected]
    password: "My_Password"
  key: mail.smtp
- data:
    url: http://192.3.239.176:9876/
    timeout: 10
  key: sms.custom

louischan-oursky Jul 9, 2024
Maintainer

Did you see any error logs in the container logs?

ilyas-sudo Jul 9, 2024
Author

Share me your email please i will contact you through email and will share my server credentials with you should check everything please that where could i make the mistake i am stuck in the project from last two weeks

ilyas-sudo Jul 10, 2024
Author

it give me audit_log table but i check in database table this table exists

root@racknerd-2b1f8ff:/home/myapp# docker-compose logs authgear
WARN[0000] /home/myapp/docker-compose.yaml: version is obsolete
authgear-1 | Updating certificates in /etc/ssl/certs...
authgear-1 | 0 added, 0 removed; done.
authgear-1 | Running hooks in /etc/ca-certificates/update.d...
authgear-1 | done.
authgear-1 | 2024/07/10 06:16:11 maxprocs: Leaving GOMAXPROCS=2: CPU quota undefined
authgear-1 | [Sentry] 2024/07/10 06:16:11 Release detection failed: exec: "git": executable file not found in $PATH
authgear-1 | [Sentry] 2024/07/10 06:16:11 Some Sentry features will not be available. See https://docs.sentry.io/product/releases/.
authgear-1 | [Sentry] 2024/07/10 06:16:11 To stop seeing this message, pass a Release to sentry.Init or set the SENTRY_RELEASE environment variable.
authgear-1 | [Sentry] 2024/07/10 06:16:11 Sentry client initialized with an empty DSN. Using noopTransport. No events will be delivered.
authgear-1 | [Sentry] 2024/07/10 06:16:11 Integration installed: ContextifyFrames
authgear-1 | [Sentry] 2024/07/10 06:16:11 Integration installed: Environment
authgear-1 | [Sentry] 2024/07/10 06:16:11 Integration installed: Modules
authgear-1 | [Sentry] 2024/07/10 06:16:11 Integration installed: IgnoreErrors
authgear-1 | [Sentry] 2024/07/10 06:16:11 Integration installed: IgnoreTransactions
authgear-1 | [Sentry] 2024/07/10 06:16:11 Integration installed: GlobalTags
authgear-1 | time="2024-07-10T06:16:11Z" level=info msg="authgear (version git-5207d60ea98a)" logger=server
authgear-1 | time="2024-07-10T06:16:11Z" level=warning msg="development mode is ON - do not use in production" logger=server
authgear-1 | [Sentry] 2024/07/10 06:16:11 Event dropped due to noopTransport usage.
authgear-1 | time="2024-07-10T06:16:11Z" level=info msg="starting Main Server on http://0.0.0.0:3000" logger=server
authgear-1 | time="2024-07-10T06:16:11Z" level=info msg="starting Main Internal Server on http://0.0.0.0:13000" logger=server
authgear-1 | time="2024-07-10T06:16:11Z" level=info msg="starting Admin API Server on http://0.0.0.0:3002" logger=server
authgear-1 | time="2024-07-10T06:16:11Z" level=info msg="starting Admin API Internal Server on http://0.0.0.0:13002" logger=server
authgear-1 | time="2024-07-10T06:16:11Z" level=debug msg="open redis connection" idle_connection_timeout_seconds=300 logger=globalredis-handle max_connection_lifetime_seconds=900 max_idle_connection=2 max_open_connection=10000
authgear-1 | time="2024-07-10T06:16:11Z" level=debug msg="open redis connection" idle_connection_timeout_seconds=300 logger=globalredis-handle max_connection_lifetime_seconds=900 max_idle_connection=2 max_open_connection=10000
authgear-1 | time="2024-07-10T06:16:11Z" level=info msg="starting Resolver Server on http://0.0.0.0:3001" logger=server
authgear-1 | time="2024-07-10T06:16:11Z" level=info msg="starting Resolver Internal Server on http://0.0.0.0:13001" logger=server
authgear-1 | time="2024-07-10T06:16:11Z" level=debug msg="serving request" logger=request request.header.host= request.header.x-forwarded-host= request.header.x-original-host= request.host="192.3.239.176:3000" request.url="/_internals/ws?session_updated_after=1720592101"
authgear-1 | time="2024-07-10T06:16:11Z" level=debug msg="open database" app=my-app conn_max_idle_time_seconds=300 conn_max_lifetime_seconds=1800 logger=db-handle max_idle_conns=3 max_open_conns=3
authgear-1 | time="2024-07-10T06:16:11Z" level=debug msg="open redis connection" app=my-app idle_connection_timeout_seconds=300 logger=appredis-handle max_connection_lifetime_seconds=900 max_idle_connection=2 max_open_connection=10000
authgear-1 | time="2024-07-10T06:16:11Z" level=debug msg="reject websocket connection" app=my-app error="session not found" logger=pubsub-http-handler
authgear-1 | time="2024-07-10T06:16:12Z" level=debug msg="canceled root context" app=my-app logger=pubsub-http-handler
authgear-1 | time="2024-07-10T06:16:17Z" level=debug msg="serving request" logger=request request.header.host= request.header.x-forwarded-host= request.header.x-original-host= request.host="192.3.239.176:3000" request.url="/signup?x_step=P9VXK8AN5XS9S5JJBS63VBG67AAHVX7T"
authgear-1 | time="2024-07-10T06:16:17Z" level=debug msg="open database" app=my-app conn_max_idle_time_seconds=300 conn_max_lifetime_seconds=1800 logger=db-handle max_idle_conns=3 max_open_conns=3
authgear-1 | time="2024-07-10T06:16:17Z" level=debug msg="open database" app=my-app conn_max_idle_time_seconds=300 conn_max_lifetime_seconds=1800 logger=db-handle max_idle_conns=3 max_open_conns=3
authgear-1 | time="2024-07-10T06:16:17Z" level=debug msg="open redis connection" app=my-app idle_connection_timeout_seconds=300 logger=analyticredis-handle max_connection_lifetime_seconds=900 max_idle_connection=2 max_open_connection=10000
authgear-1 | time="2024-07-10T06:16:18Z" level=debug msg="serving request" logger=request request.header.host= request.header.x-forwarded-host= request.header.x-original-host= request.host="192.3.239.176:3000" request.url=/static/en/app_logo.7312f47fab1b0c07ce42b5372b0d9c47.png
authgear-1 | time="2024-07-10T06:16:20Z" level=debug msg="serving request" logger=request request.header.host= request.header.x-forwarded-host= request.header.x-original-host= request.host="192.3.239.176:3000" request.url=/static/en/favicon.b1deece729a4329a20de5635c139382b.png
authgear-1 | time="2024-07-10T06:16:20Z" level=debug msg="serving request" logger=request request.header.host= request.header.x-forwarded-host= request.header.x-original-host= request.host="192.3.239.176:3000" request.url=/_internals/ws
authgear-1 | time="2024-07-10T06:16:20Z" level=debug msg="open database" app=my-app conn_max_idle_time_seconds=300 conn_max_lifetime_seconds=1800 logger=db-handle max_idle_conns=3 max_open_conns=3
authgear-1 | time="2024-07-10T06:16:20Z" level=debug msg="reject websocket connection" app=my-app error="session not found" logger=pubsub-http-handler
authgear-1 | time="2024-07-10T06:16:20Z" level=debug msg="canceled root context" app=my-app logger=pubsub-http-handler
authgear-1 | time="2024-07-10T06:16:21Z" level=debug msg="open redis connection" idle_connection_timeout_seconds=300 logger=globalredis-handle max_connection_lifetime_seconds=900 max_idle_connection=2 max_open_connection=10000
authgear-1 | time="2024-07-10T06:16:21Z" level=debug msg="open redis connection" idle_connection_timeout_seconds=300 logger=globalredis-handle max_connection_lifetime_seconds=900 max_idle_connection=2 max_open_connection=10000
authgear-1 | time="2024-07-10T06:16:24Z" level=debug msg="serving request" logger=request request.header.host= request.header.x-forwarded-host= request.header.x-original-host= request.host="192.3.239.176:3000" request.url="/signup?x_step=P9VXK8AN5XS9S5JJBS63VBG67AAHVX7T"
authgear-1 | time="2024-07-10T06:16:24Z" level=debug msg="open database" app=my-app conn_max_idle_time_seconds=300 conn_max_lifetime_seconds=1800 logger=db-handle max_idle_conns=3 max_open_conns=3
authgear-1 | time="2024-07-10T06:16:24Z" level=debug msg="open database" app=my-app conn_max_idle_time_seconds=300 conn_max_lifetime_seconds=1800 logger=db-handle max_idle_conns=3 max_open_conns=3
authgear-1 | time="2024-07-10T06:16:24Z" level=debug msg="open redis connection" app=my-app idle_connection_timeout_seconds=300 logger=appredis-handle max_connection_lifetime_seconds=900 max_idle_connection=2 max_open_connection=10000
authgear-1 | time="2024-07-10T06:16:24Z" level=debug msg="check rate limit" app=my-app global=false key="AccountEnumerationPerIP:182.180.86.132" logger=rate-limit ok=true timeToAct="2024-07-10 06:15:36.511 +0000 UTC"
authgear-1 | time="2024-07-10T06:16:24Z" level=debug msg="open redis connection" app=my-app idle_connection_timeout_seconds=300 logger=appredis-handle max_connection_lifetime_seconds=900 max_idle_connection=2 max_open_connection=10000
authgear-1 | time="2024-07-10T06:16:24Z" level=debug msg="open redis connection" app=my-app idle_connection_timeout_seconds=300 logger=appredis-handle max_connection_lifetime_seconds=900 max_idle_connection=2 max_open_connection=10000
authgear-1 | time="2024-07-10T06:16:24Z" level=debug msg="check usage limit" app=my-app key="app:my-app:usage-limit:Email" logger=usage-limit pass=true tokens=99999
authgear-1 | time="2024-07-10T06:16:24Z" level=debug msg="open redis connection" app=my-app idle_connection_timeout_seconds=300 logger=appredis-handle max_connection_lifetime_seconds=900 max_idle_connection=2 max_open_connection=10000
authgear-1 | time="2024-07-10T06:16:24Z" level=debug msg="check rate limit" app=my-app global=false key="MessagingEmailPerIP:182.180.86.132" logger=rate-limit ok=true timeToAct="2024-07-10 06:15:25.153 +0000 UTC"
authgear-1 | time="2024-07-10T06:16:24Z" level=debug msg="open redis connection" app=my-app idle_connection_timeout_seconds=300 logger=appredis-handle max_connection_lifetime_seconds=900 max_idle_connection=2 max_open_connection=10000
authgear-1 | time="2024-07-10T06:16:24Z" level=debug msg="check rate limit" app=my-app global=true key="MessagingEmailPerTarget:[email protected]" logger=rate-limit ok=true timeToAct="2024-07-09 07:14:00.553 +0000 UTC"
authgear-1 | time="2024-07-10T06:16:24Z" level=debug msg="open redis connection" app=my-app idle_connection_timeout_seconds=300 logger=appredis-handle max_connection_lifetime_seconds=900 max_idle_connection=2 max_open_connection=10000
authgear-1 | time="2024-07-10T06:16:24Z" level=debug msg="check rate limit" app=my-app global=false key="MessagingEmailPerTarget:[email protected]" logger=rate-limit ok=true timeToAct="2024-07-09 07:14:00.554 +0000 UTC"
authgear-1 | time="2024-07-10T06:16:24Z" level=debug msg="open redis connection" app=my-app idle_connection_timeout_seconds=300 logger=appredis-handle max_connection_lifetime_seconds=900 max_idle_connection=2 max_open_connection=10000
authgear-1 | time="2024-07-10T06:16:24Z" level=debug msg="check rate limit" app=my-app global=false key="VerificationCooldownEmail:[email protected]" logger=rate-limit ok=true timeToAct="2024-07-10 06:17:24.554 +0000 UTC"
authgear-1 | time="2024-07-10T06:16:24Z" level=debug msg="open redis connection" app=my-app idle_connection_timeout_seconds=300 logger=appredis-handle max_connection_lifetime_seconds=900 max_idle_connection=2 max_open_connection=10000
authgear-1 | time="2024-07-10T06:16:24Z" level=debug msg="open redis connection" app=my-app idle_connection_timeout_seconds=300 logger=appredis-handle max_connection_lifetime_seconds=900 max_idle_connection=2 max_open_connection=10000
authgear-1 | time="2024-07-10T06:16:24Z" level=debug msg="persisting event" app=my-app event="&{0000000000000001 1 email.sent 0xc0049df4d0 {1720592184 user [en-US en] en 182.180.86.132 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 my-app } true}" logger=audit-sink
authgear-1 | time="2024-07-10T06:16:24Z" level=debug msg="open database" app=my-app conn_max_idle_time_seconds=300 conn_max_lifetime_seconds=1800 logger=db-handle max_idle_conns=3 max_open_conns=3
authgear-1 | time="2024-07-10T06:16:24Z" level=error msg="failed to dispatch nonblocking error event" app=my-app error="pq: relation "public._audit_log" does not exist" logger=event stack="[log.(*StackHook).Fire at /src/pkg/util/log/stack_hook.go:23 logrus.LevelHooks.Fire at /go/pkg/mod/github.com/sirupsen/[email protected]/hooks.go:28 logrus.(*Entry).fireHooks at /go/pkg/mod/github.com/sirupsen/[email protected]/entry.go:280 logrus.(*Entry).log at /go/pkg/mod/github.com/sirupsen/[email protected]/entry.go:242 logrus.(*Entry).Log at /go/pkg/mod/github.com/sirupsen/[email protected]/entry.go:304 logrus.(*Entry).Error at /go/pkg/mod/github.com/sirupsen/[email protected]/entry.go:333 event.(*Service).DispatchEventImmediately at /src/pkg/lib/event/service.go:124 messaging.(*EmailMessage).Send at /src/pkg/lib/messaging/message_email.go:20 otp.(*MessageSender).sendEmail at /src/pkg/lib/authn/otp/sender.go:272 otp.(*MessageSender).Send at /src/pkg/lib/authn/otp/sender.go:244 nodes.(*NodeVerifyIdentity).SendCode at /src/pkg/lib/interaction/nodes/verify_identity.go:137 nodes.(*EdgeVerifyIdentity).Instantiate at /src/pkg/lib/interaction/nodes/verify_identity.go:37 interaction.(*Graph).accept at /src/pkg/lib/interaction/graph.go:375 interaction.(*Service).Accept at /src/pkg/lib/interaction/service.go:150 webapp.(*Service2).runGraph.func1 at /src/pkg/auth/webapp/service2.go:405 interaction.(*Service).DryRun at /src/pkg/lib/interaction/service.go:89 webapp.(*Service2).runGraph at /src/pkg/auth/webapp/service2.go:384 webapp.(*Service2).doPost at /src/pkg/auth/webapp/service2.go:200 webapp.(*Service2).PostWithIntent at /src/pkg/auth/webapp/service2.go:171 webapp.(*Controller).EntryPointPost at /src/pkg/auth/handler/webapp/controller.go:229 webapp.(*SignupHandler).ServeHTTP.func3 at /src/pkg/auth/handler/webapp/signup.go:156 db.(*HookHandle).WithTx at /src/pkg/lib/infra/db/hook_handle.go:89 webapp.(*Controller).Serve at /src/pkg/auth/handler/webapp/controller.go:161 webapp.(*SignupHandler).ServeHTTP at /src/pkg/auth/handler/webapp/signup.go:180 auth.NewRouter.(*RootProvider).Handler.func75 at /src/pkg/lib/deps/providers.go:183 http.HandlerFunc.ServeHTTP at /usr/local/go/src/net/http/server.go:2166 webapp.(*ImplementationSwitcherHandler).ServeHTTP at /src/pkg/auth/handler/webapp/implementation_switcher.go:64 webapp.(*VisitorIDMiddleware).Handle.func1 at /src/pkg/auth/webapp/visitor_id_middleware.go:28 http.HandlerFunc.ServeHTTP at /usr/local/go/src/net/http/server.go:2166 auth.NewRouter.(*RootProvider).Middleware.func46.1 at /src/pkg/lib/deps/providers.go:197 http.HandlerFunc.ServeHTTP at /usr/local/go/src/net/http/server.go:2166 webapp.(*AuthEntryPointMiddleware).Handle.func1 at /src/pkg/auth/handler/webapp/auth_entry_point_middleware.go:51 http.HandlerFunc.ServeHTTP at /usr/local/go/src/net/http/server.go:2166 auth.NewRouter.(*RootProvider).Middleware.func45.1 at /src/pkg/lib/deps/providers.go:197 http.HandlerFunc.ServeHTTP at /usr/local/go/src/net/http/server.go:2166 webapp.(*RequireAuthenticationEnabledMiddleware).Handle.RequireAuthenticationEnabledMiddleware.Handle.func1 at /src/pkg/auth/webapp/require_authentication_enabled_middleware.go:19 http.HandlerFunc.ServeHTTP at /usr/local/go/src/net/http/server.go:2166 auth.NewRouter.(*RootProvider).Middleware.func44.1 at /src/pkg/lib/deps/providers.go:197 http.HandlerFunc.ServeHTTP at /usr/local/go/src/net/http/server.go:2166 webapp.(*WeChatRedirectURIMiddleware).Handle.func1 at /src/pkg/auth/webapp/wechat_redirect_uri_middleware.go:63 http.HandlerFunc.ServeHTTP at /usr/local/go/src/net/http/server.go:2166 auth.NewRouter.func4.(*RootProvider).Middleware.4.1 at /src/pkg/lib/deps/providers.go:197 http.HandlerFunc.ServeHTTP at /usr/local/go/src/net/http/server.go:2166 webapp.(*DynamicCSPMiddleware).Handle.func1 at /src/pkg/auth/webapp/dynamic_csp_middleware.go:95 http.HandlerFunc.ServeHTTP at /usr/local/go/src/net/http/server.go:2166 auth.NewRouter.func4.(*RootProvider).Middleware.3.1 at /src/pkg/lib/deps/providers.go:197 http.HandlerFunc.ServeHTTP at /usr/local/go/src/net/http/server.go:2166 csrf.(*csrf).ServeHTTP at /go/pkg/mod/github.com/gorilla/[email protected]/csrf.go:306 webapp.(*CSRFMiddleware).Handle.func1 at /src/pkg/auth/webapp/csrf_middleware.go:70 http.HandlerFunc.ServeHTTP at /usr/local/go/src/net/http/server.go:2166 auth.NewRouter.func4.(*RootProvider).Middleware.2.1 at /src/pkg/lib/deps/providers.go:197 http.HandlerFunc.ServeHTTP at /usr/local/go/src/net/http/server.go:2166 webapp.(*CSRFDebugMiddleware).Handle.func1 at /src/pkg/auth/webapp/csrf_debug_middleware.go:19 http.HandlerFunc.ServeHTTP at /usr/local/go/src/net/http/server.go:2166 auth.NewRouter.func4.(*RootProvider).Middleware.1.1 at /src/pkg/lib/deps/providers.go:197 http.HandlerFunc.ServeHTTP at /usr/local/go/src/net/http/server.go:2166 webapp.(*ImplementationSwitcherMiddleware).Handle.func1 at /src/pkg/auth/handler/webapp/implementation_switcher.go:46 http.HandlerFunc.ServeHTTP at /usr/local/go/src/net/http/server.go:2166 auth.NewRouter.func3.(*RootProvider).Middleware.8.1 at /src/pkg/lib/deps/providers.go:197 http.HandlerFunc.ServeHTTP at /usr/local/go/src/net/http/server.go:2166 weba

louischan-oursky Jul 10, 2024
Maintainer

You need to run the audit log database migration to create the necessary tables. See https://docs.authgear.com/deploy-on-your-cloud/helm#run-database-migration

ilyas-sudo · 2024-07-10T07:25:35Z

ilyas-sudo
Jul 10, 2024
Author

and also give me this error

authgear-1 | time="2024-07-10T07:21:50Z" level=warning msg="skip sending email in development mode" app=my-app body="Email Verification\n\nThis email is sent to verify [email protected] on Authgear. Use this code in the verification page.\n\n198888\n\nDon't share it with anyone. If you didn't sign in or sign up, please ignore this email.\n" logger=mail-sender recipient=[email protected] reply_to= sender=[email protected] subject="[Authgear] Email Verification Instruction"

9 replies

fungc-io Jul 12, 2024
Maintainer

@ilyas-sudo ,
the yaml files examples are provided in the comments @louischan-oursky left

Here is the example configuration

authgear.yaml

# Only changes are shown here. You keep all your original fields.
messaging:
  sms_provider: custom

authgear.secrets.yaml

# Only changes are shown here. You keep all your original fields.
# secrets is an array. You keep all your original items.
secrets:
# Add this secret to configure a custom SMS gateway
- data:
    # The URL to your simple HTTP server that bridges Authgear and your SMS provider.
    # Here I suppose your simple HTTP server serves at /
    url: http://localhost:9876/
    timeout: 10
  key: sms.custom

ilyas-sudo Jul 21, 2024
Author

Thanks for the help i have configured email now i want to configure sms for my application to receive the code. My sms provider is smsniaga
i have also created simple server for HTTPS

`package main

import (
    "bytes"
    "encoding/json"
    "fmt"
    "io/ioutil"
    "net/http"
    "net/http/httputil"
)

type SMSRequest struct {
    To      string `json:"to"`
    Message string `json:"message"`
}

func main() {
    http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
        // Log the incoming request
        b, _ := httputil.DumpRequest(r, true)
        fmt.Printf("%v\n", string(b))

        // Parse the incoming request
        var smsReq SMSRequest
        err := json.NewDecoder(r.Body).Decode(&smsReq)
        if err != nil {
            http.Error(w, err.Error(), http.StatusBadRequest)
            return
        }

        // Prepare payload for SMSNiaga
        payload := map[string]string{
            "username": "[email protected]", // Replace with your SMSNiaga username
            "password": "1234qwer",            // Replace with your SMSNiaga password
            "hp":       smsReq.To,
            "message":  smsReq.Message,
        }

        payloadBytes, err := json.Marshal(payload)
        if err != nil {
            http.Error(w, err.Error(), http.StatusInternalServerError)
            return
        }

        // Send request to SMSNiaga
        resp, err := http.Post("https://api.smsniaga.com/sendsms", "application/json", bytes.NewBuffer(payloadBytes))
        if err != nil {
            http.Error(w, err.Error(), http.StatusInternalServerError)
            return
        }
        defer resp.Body.Close()

        body, err := ioutil.ReadAll(resp.Body)
        if err != nil {
            http.Error(w, err.Error(), http.StatusInternalServerError)
            return
        }

        // Return response from SMSNiaga
        w.Header().Set("Content-Type", "application/json")
        w.WriteHeader(resp.StatusCode)
        w.Write(body)
    })

    fmt.Println("Server is running on port 9876")
    http.ListenAndServe(":9876", nil)
}
`

And this is my authgear.yaml file

authenticator:
  oob_otp:
    sms:
      phone_otp_mode: sms
http:
  public_origin: http://my.jomauth.com
id: my-app
oauth:
  clients:
  - client_id: 0a4be83cf706630d
    name: Portal
    post_logout_redirect_uris:
    - http://portal.192.3.239.176:8000/
    redirect_uris:
    - http://portal.192.3.239.176:8000/oauth-redirect
    x_application_type: traditional_webapp
verification:
  claims:
    email:
      enabled: true
      required: true
messaging:
  sms_provider: custom

and this is my authgear.secrete.yaml file

secrets:
- data:
    database_schema: public
    database_url: postgres://postgres:postgres@db:5432/postgres?sslmode=disable
  key: db
- data:
    database_schema: public
    database_url: postgres://postgres:postgres@db:5432/postgres?sslmode=disable
  key: audit.db
- data:
    redis_url: redis://redis
  key: redis
- data:
    redis_url: redis://redis/1
  key: analytic.redis
- data:
    host: smtp.gmail.com
    port: 587
    username: [email protected]
    password: "djgl vukoop fsdk kllkm"
  key: mail.smtp
- data:
    url: http://192.3.239.176:9876/
    timeout: 10
  key: sms.custom

Could you please tell me where i should include my sms provider details in those files and which type of credentials would be needed for this . Please provide me the full configuration for sms setups. Thanks in advance and i really appreciate your response

fungc-io Jul 22, 2024
Maintainer

Hi @ilyas-sudo ,
thanks for your reply,
you don't need to provide the SMS provider details/credentials in authgear.secrete.yaml & authgear.yaml because this is handled by your HTTP server.

In authgear.secrete.yaml:

- data:
    url: http://192.3.239.176:9876/ # URL to your HTTP server
    timeout: 10
  key: sms.custom

Specify the URL to your HTTP server and the OTP message will be sent to it.

The request you will receive from Authgear looks like:

POST / HTTP/1.1
Host: localhost:9876
Accept-Encoding: gzip
Content-Length: 106
Content-Type: application/json
User-Agent: Go-http-client/1.1
X-Authgear-Body-Signature: 9597b6b964b39f5590acd0c30f98a548080de8f4759b9a707537e2faac3cbd3f

{"to":"+85251388325","body":"000000 is your Authgear verification code.\n\nDon't share it with anyone.\n"}

trackerhero Aug 6, 2024

Hi @ilyas-sudo ,

For delivering SMS, Authgear natively support Twilio only. If you are using a provider other than Twilio, then you need to write a simple HTTP server to work as a bridge between Authgear and your provider. You can refer to @louischan-oursky 's comment here on how to do it. https://github.com/orgs/authgear/discussions/4432#discussioncomment-9982599

For WhatsApp, we currently only support WATI (https://www.wati.io/), Wasapbot is not supported.

hi @fungc-io

for whatsapp, can you support other provider, if i want to use custom provider how can i do that?

fungc-io Aug 6, 2024
Maintainer

Hi @trackerhero , we currently only support WATI (https://www.wati.io/), Wasapbot is not supported.
It will require code change to add other providers.

Alternatively, you can connect to a WhatsApp gateway using your code in the SMS request handler.
Please refer to the server mentioned above:

If you are using a provider other than Twilio, then you need to write a simple HTTP server to work as a bridge between Authgear and your provider.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Authgear

Need Help Deploying Authgear with Specific Email and SMS Providers #4432

{{title}}

Replies: 6 comments 15 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Authgear

Need Help Deploying Authgear with Specific Email and SMS Providers #4432

ilyas-sudo Jul 6, 2024

root@racknerd-2b1f8ff:/home/myapp# cat authgear.yaml

Replies: 6 comments · 15 replies

pkong-ds Jul 6, 2024

ilyas-sudo Jul 6, 2024 Author

pkong-ds Jul 7, 2024

louischan-oursky Jul 8, 2024 Maintainer

ilyas-sudo Jul 8, 2024 Author

ilyas-sudo Jul 9, 2024 Author

louischan-oursky Jul 9, 2024 Maintainer

ilyas-sudo Jul 9, 2024 Author

ilyas-sudo Jul 10, 2024 Author

louischan-oursky Jul 10, 2024 Maintainer

ilyas-sudo Jul 10, 2024 Author

fungc-io Jul 12, 2024 Maintainer

ilyas-sudo Jul 21, 2024 Author

fungc-io Jul 22, 2024 Maintainer

trackerhero Aug 6, 2024

fungc-io Aug 6, 2024 Maintainer

ilyas-sudo
Jul 6, 2024

Replies: 6 comments 15 replies

pkong-ds
Jul 6, 2024

ilyas-sudo
Jul 6, 2024
Author

pkong-ds
Jul 7, 2024

louischan-oursky
Jul 8, 2024
Maintainer

ilyas-sudo
Jul 8, 2024
Author

ilyas-sudo Jul 9, 2024
Author

louischan-oursky Jul 9, 2024
Maintainer

ilyas-sudo Jul 9, 2024
Author

ilyas-sudo Jul 10, 2024
Author

louischan-oursky Jul 10, 2024
Maintainer

ilyas-sudo
Jul 10, 2024
Author

fungc-io Jul 12, 2024
Maintainer

ilyas-sudo Jul 21, 2024
Author

fungc-io Jul 22, 2024
Maintainer

fungc-io Aug 6, 2024
Maintainer