Replies: 1 comment
-
Yeah makes sense to implement it on Unfortunately we've had several issues over the last few days trying to publish our pre-release packages to MyGet which has been unavailable all day today as right now none of our published packages are no showing up on our MyGet feed. To work around this we've also published our pre-release packages to GitHub Packages: Unfortunately GitHub adds more friction which requires a Personal Access Token with read:packages so your NuGet.config would need to look like: <?xml version="1.0" encoding="utf-8"?>
<configuration>
<packageSources>
<clear />
<add key="github" value="https://nuget.pkg.github.com/ServiceStack/index.json" />
</packageSources>
<packageSourceCredentials>
<github>
<add key="Username" value="USERNAME" />
<add key="ClearTextPassword" value="TOKEN" />
</github>
</packageSourceCredentials>
</configuration> Where TOKEN is a PAT you've created with at least |
Beta Was this translation helpful? Give feedback.
-
Hi,
we recently switched our auth-features to use the
IAuthEventsAsync
-interface. As we're using multiple auth-event features, they are internally combined by theMultiAuthEvents
class. This class only implements theIAuthEvents
interface but is missing theIAuthEventsAsync
interface, so event though all*Async
methods are implemented none are called as the interface cast is always false.For now we're using a workaround with a custom
MultiAuthEvents
class which simply implements bothMultiAuthEvents, IAuthEventsAsync
and a customAuthFeature
feature which uses our customMultiAuthEvents
-class instead of the internal one.Thanks!
Beta Was this translation helpful? Give feedback.
All reactions