clownshark5503
Explore posts from servers✅ CheckPasswordSignInAsync returns fail when password is correct
Ok I followed function calls from to VerifyPasswordAsync which runs
Where VerifyHashedPassword is called I've checked that hash is the hashed password and that password is in-fact the password.
Here is my code:
Does anyone have an idea of what's going on?
35 replies
[solved]Stuck on a The input is not a valid Base-64 string error
Here is the full error message: The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters.
The error shows up when I use my login endpoint when _signInManager.CheckPasswordSignInAsync manager is called.
Here are things I've tried:
1. Encoding loginDto.Password into a base64 string
2. Modifying thesigningkey, making it longer and shorter. Making sure it takes up 64 bytes.
The stack trace is too big for discord so it'll be in a comment
SOLUTION: The problem was that the password in the database wasn't encoded in base64
11 replies
[Solved]Iterator is undefined in V-for
Hello! I have a drop down that's supposed to change based on the choice of a radio button. This works with a v-if="someOptionIsSelected" populate the dropdown with array1 v-else populate the dropdown with array2. However when I change the selection for the radio button option in v-for="option in array2" is undefined.
Does anyone understand whats going on?
edit: Uncaught (in promise) TypeError: option is undefined
2 replies
❔ My asp.net endpoint throws a error when it receives string
My endpoint takes a integer and 2 strings from the frontend. The frontend is sending a integer and 2 dates. Since these are typically turned into strings when you send it over and it throws a error about it I am rather lost.
Does anyone know what's going on?
4 replies
Popover works within the page but not within the component
I wish to have a popover appear when a user selects a certain radio button - I put the radio button selections in its own SFC but the pop doesn't work within the SFC. But if I put it in the page it works fine.
My SFC contains the following:
setup(){
const popoverTriggerList = document.querySelectorAll('[data-bs-toggle="popover"]')
const popoverList = [...popoverTriggerList].map(popoverTriggerEl => new bootstrap.Popover(popoverTriggerEl))
}
And the <template>
<input type="radio" class="btn-check" name="options" id="option1" autocomplete="off" checked>
<label class="btn btn-secondary" for="option1">Checked</label>
<input type="radio" class="btn-check" name="options" id="option2" autocomplete="off"
data-bs-container="body" data-bs-toggle="popover" data-bs-placement="right" data-bs-content="Popover Message"
>
<label class="btn btn-secondary" for="option2">Radio</label>
In my page I have wrapped ClientOnly around the component. But the following radio selection I placed in the page of the component that works is:
<div>
<input type="radio" class="btn-check" name="options" id="option1" autocomplete="off" checked>
<label class="btn btn-secondary" for="option1">Checked</label>
<input type="radio" class="btn-check" name="options" id="option2" autocomplete="off"
data-bs-container="body" data-bs-toggle="popover" data-bs-placement="right" data-bs-content="We cannot accomodate 5th Wheels longer than 40ft and Travel Trailers longer than 36ft"
>
<label class="btn btn-secondary" for="option2">Radio</label>
I am using bootstrap and I have imported the component in the page.
Can anyone help me get popover working within the component?2 replies
$fetch with POST and same origin policy error
Hi everyone, I'm trying to make a POST request with $fetch to my backend(asp.net) but I consistently get this error message. Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://localhost:myport/myendpoint. (Reason: header ‘content-type’ is not allowed according to header ‘Access-Control-Allow-Headers’ from CORS preflight response).
GET requests to my backend works. My backend CORS set up also should be permitting that the frontend makes this request. I wonder if my frontend being http:localhost:port/etc... and my backend being https:localhost:someport/etc has something to do with it but idk.
Here's my function:
async makeRes(){
const h = useRequestHeaders([''])
return await $fetch('https://localhost:port/myendpoint',{
headers:{
h
},
method: 'POST',
body:{
'message': <my-data>,
}
})
}
Whats yalls opinion?3 replies