Connecting oAuth with ASP.Net Identity Invalid Cast
I'm trying to build a new Web API on an existing ASP.Net Identity database. I'm following the basic Web API tutorial with creating a new project in VS2017 found on Microsoft's site.
https://docs.microsoft.com/en-us/aspnet/web-api/overview/security/individual-accounts-in-web-api
I would like to implement oAuth with this new Web API; however, when I make a POST to the http://localhost:12345/TOKEN url that contains the username/password of an existing user, the ApplicationUserManager FindAsync method throws an error telling me a type conversion is not valid.
The specified cast from a materialized 'System.Int32' type to the 'System.String' type is not valid.
Here is the POST I'm sending:
$("button").click(function(){
var loginData = {
grant_type: 'password',
username: 'user@somewhere.com',
password: 'password'
};
$.ajax({
type: 'POST',
url: 'http://localhost:12345/Token',
data: loginData
}).done(function (data) {
self.user(data.userName);
// Cache the access token in session storage.
sessionStorage.setItem(tokenKey, data.access_token);
});
});
Here is the C# side
public override async Task GrantResourceOwnerCredentials(OAuthGrantResourceOwnerCredentialsContext context)
{
var userManager = context.OwinContext.GetUserManager<ApplicationUserManager>();
ApplicationUser user = await userManager.FindAsync(context.UserName, context.Password);
//Rest omitted for readability
}
I compared the database tables of AspNetUsers that VS2017 creates to our existing database that I want to use and the AspNetUsers tables match in terms of column names and data types with the exception of the Id column. Our existing DB uses an INT and the one created automatically uses ncvarchar. I'm assuming this is the discrepancy, but I'm not sure why their schemas wouldn't match in the first place.
Is there a way to change the data type the Application User Manager is expecting so it's not looking for that nvarchar?
asp.net-web-api oauth-2.0 asp.net-identity
asked Nov 20 '18 at 16:44
RafikiRafiki
3181315
add a comment |
I'm trying to build a new Web API on an existing ASP.Net Identity database. I'm following the basic Web API tutorial with creating a new project in VS2017 found on Microsoft's site.
https://docs.microsoft.com/en-us/aspnet/web-api/overview/security/individual-accounts-in-web-api
I would like to implement oAuth with this new Web API; however, when I make a POST to the http://localhost:12345/TOKEN url that contains the username/password of an existing user, the ApplicationUserManager FindAsync method throws an error telling me a type conversion is not valid.
The specified cast from a materialized 'System.Int32' type to the 'System.String' type is not valid.
Here is the POST I'm sending:
$("button").click(function(){
var loginData = {
grant_type: 'password',
username: 'user@somewhere.com',
password: 'password'
};
$.ajax({
type: 'POST',
url: 'http://localhost:12345/Token',
data: loginData
}).done(function (data) {
self.user(data.userName);
// Cache the access token in session storage.
sessionStorage.setItem(tokenKey, data.access_token);
});
});
Here is the C# side
public override async Task GrantResourceOwnerCredentials(OAuthGrantResourceOwnerCredentialsContext context)
{
var userManager = context.OwinContext.GetUserManager<ApplicationUserManager>();
ApplicationUser user = await userManager.FindAsync(context.UserName, context.Password);
//Rest omitted for readability
}
I compared the database tables of AspNetUsers that VS2017 creates to our existing database that I want to use and the AspNetUsers tables match in terms of column names and data types with the exception of the Id column. Our existing DB uses an INT and the one created automatically uses ncvarchar. I'm assuming this is the discrepancy, but I'm not sure why their schemas wouldn't match in the first place.
Is there a way to change the data type the Application User Manager is expecting so it's not looking for that nvarchar?
asp.net-web-api oauth-2.0 asp.net-identity
asked Nov 20 '18 at 16:44
RafikiRafiki
3181315
Although the problems are different, this post seems to contain the same solution. stackoverflow.com/questions/34505904/…
– Rafiki
Nov 20 '18 at 18:54
add a comment |
I'm trying to build a new Web API on an existing ASP.Net Identity database. I'm following the basic Web API tutorial with creating a new project in VS2017 found on Microsoft's site.
https://docs.microsoft.com/en-us/aspnet/web-api/overview/security/individual-accounts-in-web-api
I would like to implement oAuth with this new Web API; however, when I make a POST to the http://localhost:12345/TOKEN url that contains the username/password of an existing user, the ApplicationUserManager FindAsync method throws an error telling me a type conversion is not valid.
The specified cast from a materialized 'System.Int32' type to the 'System.String' type is not valid.
Here is the POST I'm sending:
$("button").click(function(){
var loginData = {
grant_type: 'password',
username: 'user@somewhere.com',
password: 'password'
};
$.ajax({
type: 'POST',
url: 'http://localhost:12345/Token',
data: loginData
}).done(function (data) {
self.user(data.userName);
// Cache the access token in session storage.
sessionStorage.setItem(tokenKey, data.access_token);
});
});
Here is the C# side
public override async Task GrantResourceOwnerCredentials(OAuthGrantResourceOwnerCredentialsContext context)
{
var userManager = context.OwinContext.GetUserManager<ApplicationUserManager>();
ApplicationUser user = await userManager.FindAsync(context.UserName, context.Password);
//Rest omitted for readability
}
I compared the database tables of AspNetUsers that VS2017 creates to our existing database that I want to use and the AspNetUsers tables match in terms of column names and data types with the exception of the Id column. Our existing DB uses an INT and the one created automatically uses ncvarchar. I'm assuming this is the discrepancy, but I'm not sure why their schemas wouldn't match in the first place.
Is there a way to change the data type the Application User Manager is expecting so it's not looking for that nvarchar?
asp.net-web-api oauth-2.0 asp.net-identity
asked Nov 20 '18 at 16:44
RafikiRafiki
3181315
I'm trying to build a new Web API on an existing ASP.Net Identity database. I'm following the basic Web API tutorial with creating a new project in VS2017 found on Microsoft's site.
https://docs.microsoft.com/en-us/aspnet/web-api/overview/security/individual-accounts-in-web-api
I would like to implement oAuth with this new Web API; however, when I make a POST to the http://localhost:12345/TOKEN url that contains the username/password of an existing user, the ApplicationUserManager FindAsync method throws an error telling me a type conversion is not valid.
The specified cast from a materialized 'System.Int32' type to the 'System.String' type is not valid.
Here is the POST I'm sending:
$("button").click(function(){
var loginData = {
grant_type: 'password',
username: 'user@somewhere.com',
password: 'password'
};
$.ajax({
type: 'POST',
url: 'http://localhost:12345/Token',
data: loginData
}).done(function (data) {
self.user(data.userName);
// Cache the access token in session storage.
sessionStorage.setItem(tokenKey, data.access_token);
});
});
Here is the C# side
public override async Task GrantResourceOwnerCredentials(OAuthGrantResourceOwnerCredentialsContext context)
{
var userManager = context.OwinContext.GetUserManager<ApplicationUserManager>();
ApplicationUser user = await userManager.FindAsync(context.UserName, context.Password);
//Rest omitted for readability
}
I compared the database tables of AspNetUsers that VS2017 creates to our existing database that I want to use and the AspNetUsers tables match in terms of column names and data types with the exception of the Id column. Our existing DB uses an INT and the one created automatically uses ncvarchar. I'm assuming this is the discrepancy, but I'm not sure why their schemas wouldn't match in the first place.
Is there a way to change the data type the Application User Manager is expecting so it's not looking for that nvarchar?
asp.net-web-api oauth-2.0 asp.net-identity
asp.net-web-api oauth-2.0 asp.net-identity
asked Nov 20 '18 at 16:44
RafikiRafiki
3181315
asked Nov 20 '18 at 16:44
RafikiRafiki
3181315
edited Nov 20 '18 at 17:12
Rafiki
asked Nov 20 '18 at 16:44
RafikiRafiki
3181315
asked Nov 20 '18 at 16:44
RafikiRafiki
3181315
asked Nov 20 '18 at 16:44
RafikiRafiki
3181315
3181315
Although the problems are different, this post seems to contain the same solution. stackoverflow.com/questions/34505904/…
– Rafiki
Nov 20 '18 at 18:54
add a comment |
Although the problems are different, this post seems to contain the same solution. stackoverflow.com/questions/34505904/…
– Rafiki
Nov 20 '18 at 18:54
Although the problems are different, this post seems to contain the same solution. stackoverflow.com/questions/34505904/…
– Rafiki
Nov 20 '18 at 18:54
Although the problems are different, this post seems to contain the same solution. stackoverflow.com/questions/34505904/…
– Rafiki
Nov 20 '18 at 18:54
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53397661%2fconnecting-oauth-with-asp-net-identity-invalid-cast%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53397661%2fconnecting-oauth-with-asp-net-identity-invalid-cast%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Although the problems are different, this post seems to contain the same solution. stackoverflow.com/questions/34505904/…
– Rafiki
Nov 20 '18 at 18:54