.NET (Core and Framework)

23-Aug-22 22:15

This question is about a net core Web app

Hi all , if I put this line in _ViewImports.cshtml (where IPageSettings is in the IServiceCollection)

@inject IPagingSettings PageSettings;

PageSettings is available in all my views EXCEPT _layout.cshtml, anyone know why ? I can't find anything with Mr Google

Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP

Richard Deeming23-Aug-22 22:47

23-Aug-22 22:47

According to the documentation[^], _ViewImports should apply to every page, including layouts and partial views, whereas _ViewStart doesn't apply to layouts or partial views.

There must be something else going on. What's the hierarchy of your views folder, and what's the error message you're getting?

"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer

pkfox23-Aug-22 23:13

23-Aug-22 23:13

It's the standard hierarchy Richard - _ViewImports.cshtml is in the root Views folder - there is no error it's (the var) not available when I try and use it with @PageSettings, in all the other views I get intellisense

Edit
I should mention that, if I put the same @inject statement directly in _layout.cshtml it works

modified 24-Aug-22 5:21am.

Richard Deeming23-Aug-22 23:29

23-Aug-22 23:29

"Not available" as in "not listed by intellisense", or does it not compile if you try to use it?

"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer

pkfox23-Aug-22 23:44

Problem with Azure AD JWT - solved

23-Aug-22 23:44

Good call Richard it does actually work but I don't like red squigglies - I've noticed the same with the using statements, same thing intellisense works in all views except _layout where I'm prompted to add the full namespace.class

pkfox18-Aug-22 5:56

Rest API always return 401 status code

18-Aug-22 5:56

I have an API and a client registered for authorization on Azure AD.
When making a call to an endpoint which has the Authorize attribute on, I'm getting a 401 unauthorized response. I think the problem is, I'm using the wrong clientid/ResourceId combination when acquiring the token ( I get a token but it's invalid ) - anyone know which clientid/ResourceId I should be using when requesting the token ?

On the API registration in Azure the values are

ClientId: "0efb6359-0d88-4196-9f53-054b042b2ae1"
Instance: https://login.microsoftonline.com/",
ResourceId: "api://0efb6359-0d88-4196-9f53-054b042b2ae1/.default", // this should be 41eeebbd-ea7f-4f49-a936-1624b6cb9c72
TenantId: "90fff3ee-9a7c-4eb1-8259-4d8c6bf6ca90"

and the client

ClientId: "41eeebbd-ea7f-4f49-a936-1624b6cb9c72",
Instance: "https://login.microsoftonline.com/",
ResourceId: "api://0efb6359-0d88-4196-9f53-054b042b2ae1/.default" // this should be 41eeebbd-ea7f-4f49-a936-1624b6cb9c72
TenantId: "90fff3ee-9a7c-4eb1-8259-4d8c6bf6ca90"

I'm confused Wink | ;)

I've tried swapping out the clientid/ResourceId but to no avail hope this makes sense

Edit
I figured it out you have to put the clientid of the Client in the resourceid of the API

modified 19-Aug-22 11:30am.

Mou_kol10-Aug-22 0:59

Re: Rest API always return 401 status code

10-Aug-22 0:59

I am working with Nasdaq Fund Network Data Service first time. i am calling their one of the API where passing user id,pwd and access key but always getting 401 status code. i am not able to figure out what is wrong in my http call. please some one have a look at the code and tell me where i made the mistake for which i am getting 401 status code instead of right response.

here is my sample code where i could not share actual credentials and access key.

string url = "https://nfn.nasdaq.com/servicecall/tempsession";
 Uri u = new Uri(url);
    
 string username = "test1";
 string password = "test1";
 string accessKey = "my key";
    
 var payload = new Dictionary<string, string>
 {
   {"username", username},
   {"password", password},
   { "accesskey", accessKey}
 };
    
 string strPayload = JsonConvert.SerializeObject(payload);
 HttpContent c = new StringContent(strPayload, Encoding.UTF8, "application/x-www-form-urlencoded");
    
 var response = string.Empty;
 ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12 | SecurityProtocolType.Tls11;
 using (var client = new HttpClient())
 {
  //client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Bearer", accessKey);
  //client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Authorization", "Bearer " + accessKey);
    
  HttpRequestMessage request = new HttpRequestMessage
  {
  Method = HttpMethod.Post,
  RequestUri = u,
  Content = c
  };
    
  var result = client.SendAsync(request).Result;
  if (result.IsSuccessStatusCode)
  {
  response = result.StatusCode.ToString();
  }
 }

modified 10-Aug-22 9:50am.

Gerry Schmitz10-Aug-22 4:05

Gerry Schmitz

10-Aug-22 4:05

I think there's more to it than sending some raw login information.

GitHub - Nasdaq/NasdaqCloudDataService-SDK-Java: Nasdaq Cloud Data Service (NCDS) provides a modern and efficient method of delivery for realtime exchange data and other financial information. This repository provides an SDK for developing applicatio

"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I

Re: Rest API always return 401 status code

Mou_kol10-Aug-22 5:08

ASP.NET Core MVC: How to secure token when passing with url

10-Aug-22 5:08

i am looking for c# related call.

Mou_kol9-Aug-22 4:23

Re: ASP.NET Core MVC: How to secure token when passing with url

9-Aug-22 4:23

i got a application developed with asp.net core mvc where token is always passed with url. it seems if we pass token with each url then it is not secure way. so any time any other user can get url and appear before server as right user.

our token life is 24 hours.

sample url looks like http://localhost:48000/ACX/Default/Login?token=8kzRLdW8lQVIS0MrtlqdZJbmz9p22l33u1wspGOmLgCgEy2MG5XZ0JG1ovVZGiNX7KpAfBVn3[^]

This code is generating the token which would valid up to 24 hours:

 public IActionResult Login([FromBody]LoginModel user)  
 {  
     if (user == null)  
     {  
         return BadRequest("Invalid request");  
     }  
          
     if (user.UserName == "johncitizen" && user.Password == "abc@123")  
     {  
         var secretKey = new SymmetricSecurityKey(Encoding.UTF8.GetBytes("KeyForSignInSecret@1234"));  
         var signinCredentials = new SigningCredentials(secretKey, SecurityAlgorithms.HmacSha256);  
    
         var tokeOptions = new JwtSecurityToken(  
             issuer: "http://localhost:2000",  
             audience: "http://localhost:2000",  
             claims: new List<Claim>(),  
             expires: DateTime.Now.AddMinutes(1440), // valid till 24 hours
             signingCredentials: signinCredentials  
         );  
    
         var tokenString = new JwtSecurityTokenHandler().WriteToken(tokeOptions);  
         return Ok(new { Token = tokenString });  
     }  
     else  
     {  
         return Unauthorized();  
     }  
 }

What can we do as a result token would be secure passing through URL? I want to change flow bit in such a way that if another user copy and paste the same URL, then he will not be able to access protected resource. So how to achieve and secure long life token?

Please guide me with approach in details. Thanks

Richard Deeming9-Aug-22 5:12

Re: ASP.NET Core MVC: How to secure token when passing with url

9-Aug-22 5:12

For a user browsing your site, the token should be sent back in an HTTP-only, secure, same-site cookie.
Use cookie authentication without ASP.NET Core Identity | Microsoft Docs[^]

"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer

Mou_kol10-Aug-22 0:58

Get this error when returning view

10-Aug-22 0:58

Thanks for guide line.

pkfox3-Aug-22 22:41

Re: Get this error when returning view

3-Aug-22 22:41

This is driving me mad!!!

My hobby project a net core 6 Web app was running perfectly until yesterday - I'm now getting this error message whenever I try and return a view. I've obviously done something but I can't for the life of me think what. I can't catch the error either it just bombs and shows this error in the browser - any ideas ? The app runs as a daemon on a Debian box.

MissingMethodException: Method not found: Microsoft.AspNetCore.Razor.Language.RazorConfiguration Microsoft.AspNetCore.Razor.Language.RazorConfiguration.Create(Microsoft.AspNetCore.Razor.Language.RazorLanguageVersion, System.String, System.Collections.Generic.IEnumerable`1<Microsoft.AspNetCore.Razor.Language.RazorExtension>)
Microsoft.AspNetCore.Mvc.Razor.Extensions.RazorPageDocumentClassifierPass..cctor()

Richard Deeming3-Aug-22 23:25

Re: Get this error when returning view

3-Aug-22 23:25

At a guess, you've either updated some libraries, or the .NET SDK, and something is now outdated.

Looking at the history[^], that method existed in the version of the code from November 2018:
razor-compiler/RazorConfiguration.cs at 32ff07c6d4a8037c61a5c75c26fc5f805da19b3a · dotnet/razor-compiler · GitHub[^]

But in March 2021, an optional parameter was added:
razor-compiler/RazorConfiguration.cs at f26e545a6712f186c84ed4ed956927be8ab52af6 · dotnet/razor-compiler · GitHub[^]

You have a library compiled against the 2018 version which is now running against the 2021 (or later) version.

I suspect you've updated the Microsoft.AspNetCore.Razor.Language[^] package, but not updated the Microsoft.AspNetCore.Mvc.Razor.Extensions[^] package to match. However, it's possible that your project doesn't directly reference either of these packages, and they're being pulled in as a transitive dependency of another package instead. You may need to dig through the dependency tree of each NuGet package you've referenced.

"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer

pkfox3-Aug-22 23:40