-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Random text being shown in email value in Token Authentication, instead of "string" as default value #852
Comments
Hi again. could someone tell me what could be wrong here??? I am still trying to solve this error but can't figure out what is causing this random string to occur. Kindly reply as soon as possible. |
Check : TokensController-> GetIpAddress() -> as master |
Following is the TokensController. Still this bug is not fixed. public sealed class TokensController : VersionedNeutralApiController
} The random string changes on pressing the reset button in token authentication. |
private string GetIpAddress() => |
Still not fixed. Is there any other way to fix this bug??? Is it possible that any nuget package is not compatible with this ??? |
Fixed it some how. I uninstalled (ZymLabs.NSwag.FluentValidation.AspNetCore) nuget package and installed a previous version of this package. It did not work but then I reinstalled the latest version (0.6.2) of (ZymLabs.NSwag.FluentValidation.AspNetCore) and the bug was gone. Thanks anyway. |
Describe the bug
A clear and concise description of what the bug is.
Expected behavior
![image](https://user-images.githubusercontent.com/46562878/232223389-bc27ba0d-8cc6-4181-8d03-09e3675343db.png)
Following should be displayed:
{
"email": "string",
"password": "string"
}
Instead it is displaying as follows:
{
"email": "hy3%5s4uFhBD<yJfxBfsTT@BBEM;coO2irsX[}{AZ -qKKt(e:x",
"password": "string"
}
Screenshots
![image](https://user-images.githubusercontent.com/46562878/232223344-d05086bd-6200-4e4c-87b0-6e1a1c35d8cf.png)
Maybe this error is occurring on my end. but I can't figure out how to solve this issue.
The text was updated successfully, but these errors were encountered: