Scheduler

Azure Scheduler allows you to invoke actions that call HTTP/S endpoints or post messages to a storage queue on any schedule. In Scheduler, you can create jobs that reliably call services either inside or outside of Windows Azure and run those jobs right away, on a regular or irregular schedule, or set them to run at a future date.

If you have any feedback on Azure Scheduler, we’d love to hear it.

  1. Add support for specifying resourceId when setting up Azure AD OAuth for Scheduler

    https://docs.microsoft.com/en-us/azure/scheduler/scheduler-outbound-authentication#request-body-for-activedirectoryoauth-authentication

    Missing resourceId will cause the token to miss any app specific roles that might be configured.

    Now, in our our endpoints that are called with scheduler, we are forced to remove any role-checking attributes. This leaves us more vulnerable to attacks since we check authentication only and not authentication + authorization.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  2. auth0 authentication options

    Hi

    We want to use the scheduler to call (POST) an API endpoint that we currently have secured with JWT tokens.

    As security provider we are using Auth0.

    We noticed that there are some configurations regarding authentication, but seems that there is no way of configuring Auth0 here. The settings needed are (almost) the same as for ActiveDirectoryOAuth.

    Are there any plans currently to support this ? Are there any workarounds that we can apply?

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
1 3 Next →
  • Don't see your idea?

Scheduler

Categories

Feedback and Knowledge Base