Martin Comments - Answer Overflow

Martin

Posts Comments

KKinde

•Created by Martin on 8/30/2024 in #💻┃support

User unable to login

@Oli - Kinde - I have DM'd you some more details about this issue.

6 replies

KKinde

•Created by Martin on 8/30/2024 in #💻┃support

User unable to login

@IkiTg07 - there's no way for us to collect logs because the 403 forbidden is being returned from the Kinde host which is mapped by DNS to our Kinde custom domain. My hope is that Kinde have some logs to explain why this happened.

6 replies

KKinde

•Created by Martin on 2/1/2024 in #💻┃support

Wildcards in callback URLs bug

Thanks for the response! I've sent you a couple of DMs with more details.

37 replies

KKinde

•Created by Martin on 2/1/2024 in #💻┃support

Wildcards in callback URLs bug

@Oli - Kinde - Has there been any update on this issue?

37 replies

KKinde

•Created by Martin on 2/1/2024 in #💻┃support

Wildcards in callback URLs bug

@Oli - Kinde - have you had a reply from your team about this bug?

37 replies

KKinde

•Created by Martin on 2/1/2024 in #💻┃support

Wildcards in callback URLs bug

@Oli - Kinde - I have sent you a long reply in a DM. I've done this in DM so that I can include full details of my Kinde application ID and an example full domain on which login isn't working. Can you please take a look and let me know if you have any questions?

37 replies

KKinde

•Created by Martin on 2/1/2024 in #💻┃support

Wildcards in callback URLs bug

Thanks @Oli - Kinde. Do you have any updates on the timeline for fixing the original feature? I'd really love to use the wildcarding which was announced back at the start of February, but it seems to be entirely broken by the bug we've been discussing in this thread since then.

37 replies

KKinde

•Created by Martin on 2/1/2024 in #💻┃support

Wildcards in callback URLs bug

Nope, I was wrong, it's still broken, and now the form where I enter the redirect URLs is trying to restrict me to 255 characters of config, which means I can't enter all the redirect URLs I need to for all our various QA envs, so this is actually getting a bit worse.

37 replies

KKinde

•Created by Martin on 2/1/2024 in #💻┃support

Wildcards in callback URLs bug

Actually, I can now see that this is fixed, so what I really mean is, thanks! ❤️

37 replies

KKinde

•Created by Martin on 2/1/2024 in #💻┃support

Wildcards in callback URLs bug

@Oli - Kinde - has there been any progress with this issue?

37 replies

KKinde

•Created by Martin on 2/1/2024 in #💻┃support

Wildcards in callback URLs bug

@Oli - Kinde - has there been any progress on this issue? I'd love to eliminate the manual setup I'm having to do in the Kinde console every time I deploy a new QA env.

37 replies

KKinde

•Created by Martin on 3/26/2024 in #💻┃support

User not receiving PIN to their email address

That seems to be the case. One thing to make you aware of is that we realised yesterday that the SPF DNS config on our domain (inrange.io) wasn't correctly configured to allow our Mailchimp SMTP server to send emails. We've now fixed that, but it's possible that was contributing to the issue with the customer who wasn't receiving the login codes emails. We haven't been able to confirm that yet as we haven't asked our customer to attempt another login. Although that would only explain the fact that the emails weren't getting through from our custom SMTP server. I can see that Kinde's SPF config looks valid (https://mxtoolbox.com/SuperTool.aspx?action=spf%3akinde.com&run=toolpage) and so don't think this explains why the emails weren't getting through before we switched to a custom SMTP server.

8 replies

KKinde

•Created by Martin on 3/26/2024 in #💻┃support

User not receiving PIN to their email address

@Daniel_Kinde - We've switched over to using our own custom SMTP server and confirmed that this works for us, but the user who couldn't log in has just confirmed that they're still not receiving the login code email from us. We can see in our SMTP logs that we've sent the email to them, but they don't seem to have received it. Have you made any progress talking to Spamhero about why/whether they're blocking emails from Kinde?

8 replies

KKinde

•Created by Martin on 2/1/2024 in #💻┃support

Wildcards in callback URLs bug

Thanks, I really appreciate the update

37 replies

KKinde

•Created by Martin on 3/26/2024 in #💻┃support

User not receiving PIN to their email address

@Daniel_Kinde - are there any plans to add audit logs to cover these kinds of partial login events where a user gets as far as entering their email address but doesn't complete the login? I'm very concerned that my team might have other users who are failing to login and we don't have any visibility into that right now.

8 replies

KKinde

•Created by Martin on 3/26/2024 in #💻┃support

User not receiving PIN to their email address

Thanks, I've replied to you over DM

8 replies

KKinde

•Created by Martin on 2/1/2024 in #💻┃support

Wildcards in callback URLs bug

@Dave - Kinde - do you have a timeline for when you'll be able to address this bug?

37 replies

KKinde

•Created by Martin on 2/1/2024 in #💻┃support

Wildcards in callback URLs bug

These are the HTTP Response headers after I configure a non-wildcard domain:

HTTP/2 200 
access-control-allow-credentials: true
access-control-allow-headers: *, Kinde-SDK
access-control-allow-methods: GET, POST
access-control-allow-origin: https://admin-app-inrt-960-panel-change-fixes.inrange.dev
access-control-max-age: 1728000
alt-svc: h3=":443"; ma=2592000
content-type: text/plain; charset=utf-8
date: Wed, 20 Mar 2024 15:36:09 GMT
vary: Origin
content-length: 0
X-Firefox-Spdy: h2

HTTP/2 200 
access-control-allow-credentials: true
access-control-allow-headers: *, Kinde-SDK
access-control-allow-methods: GET, POST
access-control-allow-origin: https://admin-app-inrt-960-panel-change-fixes.inrange.dev
access-control-max-age: 1728000
alt-svc: h3=":443"; ma=2592000
content-type: text/plain; charset=utf-8
date: Wed, 20 Mar 2024 15:36:09 GMT
vary: Origin
content-length: 0
X-Firefox-Spdy: h2

The missing access-control-allow-origin header is what is blocking my request from succeeding in Firefox. This looks like a bug in your implementation setting CORS headers.

37 replies

KKinde

•Created by Martin on 2/1/2024 in #💻┃support

Wildcards in callback URLs bug

This is how I'm doing auto-forwarding:

  const {
    login,
    logout,
    isLoading: isAuthLoading,
    user: kindeUser,
    getOrganization,
  } = useKindeAuth();
  const [user, setUser] = useState(undefined);

  useEffect(() => {
    if (!isAuthLoading && kindeUser) {
      setUser({
        name: `${kindeUser.given_name} ${kindeUser.family_name}`,
        email: kindeUser.email,
        family_name: kindeUser.family_name,
        given_name: kindeUser.given_name,
        picture: kindeUser.picture,
      });
    }
  }, [isAuthLoading, kindeUser]);

  if (!isAuthLoading && !kindeUser) {
    login({
      org_code: KINDE_ENVIRONMENT.KINDE_INRANGE_ORG_CODE,
      app_state: {
        redirectTo: window.location.pathname + window.location.search,
      },
    });
  }

  const {
    login,
    logout,
    isLoading: isAuthLoading,
    user: kindeUser,
    getOrganization,
  } = useKindeAuth();
  const [user, setUser] = useState(undefined);

  useEffect(() => {
    if (!isAuthLoading && kindeUser) {
      setUser({
        name: `${kindeUser.given_name} ${kindeUser.family_name}`,
        email: kindeUser.email,
        family_name: kindeUser.family_name,
        given_name: kindeUser.given_name,
        picture: kindeUser.picture,
      });
    }
  }, [isAuthLoading, kindeUser]);

  if (!isAuthLoading && !kindeUser) {
    login({
      org_code: KINDE_ENVIRONMENT.KINDE_INRANGE_ORG_CODE,
      app_state: {
        redirectTo: window.location.pathname + window.location.search,
      },
    });
  }

The issue seems to be that somehow when I'm relying on a wildcard URL the Kinde SDK ends up in the state of isAuthLoading = false and kindeUser = undefined before the POST call to exchange the code for an auth token has completed. The issue appears to be the CORS headers returned to the OPTIONS request. These are the HTTP Response headers when I only have a wildcard domain configured:

HTTP/2 200 
access-control-allow-headers: *, Kinde-SDK
access-control-allow-methods: GET, POST
access-control-max-age: 1728000
alt-svc: h3=":443"; ma=2592000
content-type: text/plain; charset=utf-8
date: Wed, 20 Mar 2024 15:29:12 GMT
vary: Origin
content-length: 0
X-Firefox-Spdy: h2

HTTP/2 200 
access-control-allow-headers: *, Kinde-SDK
access-control-allow-methods: GET, POST
access-control-max-age: 1728000
alt-svc: h3=":443"; ma=2592000
content-type: text/plain; charset=utf-8
date: Wed, 20 Mar 2024 15:29:12 GMT
vary: Origin
content-length: 0
X-Firefox-Spdy: h2

37 replies

KKinde

•Created by Martin on 2/1/2024 in #💻┃support

Wildcards in callback URLs bug

I'm currently using: * @kinde-oss/[email protected] * @kinde-oss/[email protected]

37 replies

Gaming

Programming