Skip to content
This repository was archived by the owner on Dec 13, 2018. It is now read-only.

Conversation

zippy1981
Copy link

No description provided.

/// that will be persisted through the authentication process. The ProtocolMessage can also be used to add or customize
/// Invoked before redirecting to the identity provider to authenticate. This can be used to set
/// <see cref="RedirectContext.ProtocolMessage"/>
/// that will be persisted through the authentication process. The ProtocolMessage can also be used to add or alter
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What were you trying to convey? Or did you just want to add the cref?

This is confusing two ideas. This sentence was specifically about the ability to round trip user State. Customizing the RedirectContext.ProtocolMessage is already covered in the next sentence.

@zippy1981
Copy link
Author

Ok I'll have another look tonight and fix.

@zippy1981
Copy link
Author

@Tratcher ok addressed and added some more docs.

Copy link
Member

@Tratcher Tratcher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I see what you're going for here but I don't think it makes sense to add these kinds of comments in the API docs. This seems more appropriate for a concept doc.

We don't have a generic OIDC doc, maybe we need one. The closest we have are the AAD docs: https://docs.microsoft.com/en-us/aspnet/core/security/authentication/azure-active-directory/?view=aspnetcore-2.1

/// Gets or Sets the URI used for the redirect operation.
/// </summary>
/// <remarks>If you cannot let ASP.NET rewrite the <see cref="HttpRequest.PathBase"/>
/// for you, such as through <c>ForwardedHeadersOptions</c></remarks> you can use this.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

</remarks> is out of place.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This often isn't a local uri, so these comments don't make sense.

}

/// <summary>
/// Gets or Sets the URI used for the redirect operation.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/// </summary>
/// <remarks>
/// While this can be used to rewrite the redirect URLs if the app is behind a proxy server, its best to use
/// <c>ForwardedHeadersOptions</c>. Please see: https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/proxy-load-balancer?view=aspnetcore-2.1.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can't use direct links in doc comments, the links are unstable. If it were critical we'd use a forward link.

@Eilon
Copy link
Contributor

Eilon commented Jul 27, 2018

@Tratcher can you create an aka.ms link for the doc, fix the bad XML, and merge?

@Tratcher
Copy link
Member

Tratcher commented Aug 3, 2018

Closing due to lack of follwup. The comments about forwarders do not belong here and the other changes are aesthetic only.

@Tratcher Tratcher closed this Aug 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants