#nickdnk_error
pure matrixBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1338880816876617758
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- nickdnk_unexpected, 8 minutes ago, 29 messages
- nickdnk_code, 3 days ago, 118 messages
karmic cipher
Followup to my previous thread which was closed
Not sure what I'm doing wrong here
normal sapphire
hey again, taking a look at this example
karmic cipher
Ahh, sorry, it has specifically this denied on the key. I was not aware it was a separate access level
I couldn't add this before I had added IP restrictions
or, rather I couldn't swap recent for all
It works
I apologize, I forgot about that part
Somehow I had remembered it as one access level which was just time-limited based on whether or not you had IP restrictions
Anyway, bottom line for me here is that all of this would have been avoided, if I had been able to add the Account Session access/permissions to a restricted key, like I mentioned in the other thread.
changed from RK to SK to support Account Sessions -> broke verifications -> they became older than 48 hours and got stuck in queue -> had to add IP restrictions etc. and here we are
normal sapphire
Yea we've reported that friction feedback to hopefully get it improved.
karmic cipher
Thanks, I appreciate it
normal sapphire
For this one, the issue was the necessary permissions weren't surfaced until after you added the IP restrictions?
karmic cipher
Well it's a combination of things here. I already knew that I needed a restricted key for verifications, but I had forgotten and thought that was only for post-48-hour verification data. It wasn't. And Account Sessions doesn't work at all with restricted keys, so I just replaced our restricted key with a secret key and broke our verifications.
And apparently the only solution here is to deploy two different keys, one for verifications and one for account sessions, which doesn't seem optimal to me
Like mentioned in the other thread, it's probably because account sessions is a new thing so it wasn't added as a permission on restricted keys yet
On another note, it also seems very weird to me that a secret key with IP restrictions doesn't qualify for identity verification data, but I guess that's a legal thing
normal sapphire
Yea i can't speak to that limitation specifically, I speculate similar security/privacy motivations.
karmic cipher
Probably. But to summarize: My ask here is that Account Sessions can be used with restricted keys.
Just to make that clear since we touched on multiple things here
normal sapphire
Yep, got it. That's the main feedback we filed here as the initial complicating factor.