Nishan

My feedback

  1. 28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  API Management » Security  ·  Flag idea as inappropriate…  ·  Admin →

    Basic credentials can be already validated using a combination of check header policy and expression (use named value for storing username and password).

    We could simplify this use case by implementing a “validate basic credentials” policy, hence I am keeping this under review.

    An error occurred while saving the comment
    Nishan commented  · 

    Try this

    <policies>
    <inbound>
    <set-variable name="AuthValue" value="@("Basic " + Convert.ToBase64String(System.Text.ASCIIEncoding.ASCII.GetBytes(string.Format("{0}:{1}", "{{username}}", "{{password}}"))))" />
    <trace source="arbitrary string literal">@(context.Variables.GetValueOrDefault<string>("AuthValue"))</trace>
    <check-header name="Authorization" failed-check-httpcode="401" failed-check-error-message="Not authorized" ignore-case="false">
    <value>@(context.Variables.GetValueOrDefault<string>("AuthValue"))</value>
    </check-header>
    <base />
    </inbound>
    <backend>
    <base />
    </backend>
    <outbound>
    <base />
    </outbound>
    <on-error>
    <base />
    </on-error>
    </policies>

  2. 20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Nishan commented  · 

    How do you set "auditingType": "Blob" on ARM template ?

Feedback and Knowledge Base