Does Planar Binding require you to keep concentrating on the summoning spell?

Planar binding states:

With this spell, you attempt to bind a celestial, an elemental, a fey, or a fiend to your service. The creature must be within range for the entire casting of the spell. […] At the completion of the casting, the target must make a Charisma saving throw. On a failed save, it is bound to serve you for the duration. If the creature was summoned or created by another spell, that spell’s duration is extended to match the duration of this spell.

Most summoning spells require concentration. Would the original caster be required to continue concentrating on that spell even when planar binding extends the duration?

I was inclined to say “yes” to this, but it was pointed out that upcasting planar binding extends its duration to as much as a year and a day.

At Higher Levels. When you cast this spell using a spell slot of a higher level, the duration increases to 10 days with a 6th-level slot, to 30 days with a 7th- level slot, to 180 days with an 8th-level slot, and to a year and a day with a 9th-level spell slot.

It seems really unreasonable to expect concentration to be even over these extreme lengths of time.

Am I missing something here?

So, does planar binding require the original caster to maintain concentration on the extended summoning spell when one is present?

How to keep authorization model maintainable on calls between different microservices?

In our environment (as in many others), it is often the case that one microservice must call another in order to accomplish a task.

In our environment, authentication is clear enough – we have a signed JWT containing a list of permissions and roles, as well as a user ID, client ID, and so on.

What we’re less clear on is authorization – ensuring that the authenticated client can (or can’t) do the right stuff, but that the underlying services have all the access they need to do their jobs (even if the client wouldn’t be able to do the same things directly).

We’ve examined a few different options:

  1. Each service does all of its own authorization, and if a privilege escalation is needed, it generates a “God mode” token with an otherwise unchanged payload and a different keypair and makes the call using that. The main concern here is copy/pasted authorization code, and the fact that there’ll be a strong incentive to just always enable God mode when making cross-service calls (which makes it somewhat redundant).
  2. Each service does all of its own authorization, and just forwards the user’s token if it needs to make a call. The concern here is code duplication like in option 1, and also the fact that this is likely to cause a complex interdependent web of permissions that imply other permissions that imply other permissions that… (ad nauseam), creating a maintenance headache as the number of services grows.
  3. A lightweight API gateway service that does “simple” authorization (nothing more advanced than “is this client allowed to use this endpoint at all?”), attaches a user object to the payload, and leaves more specific behaviours to the underlying services, which accept any call as being authorized out of the gate. The major concern with this option is performance and stability – the API gateway service creates a single point of failure that can make the entire system inaccessible if it malfunctions, plus creating a frequently-changing dependency for every service.

The question here is twofold:

  1. Are there any additional pitfalls to the three patterns described above that we haven’t considered?
  2. Which of these is the most common in the wild?

Note that this question is not about service mesh offerings like Istio, as we consider them to be somewhat orthogonal to this issue.

Need to upgrade to 19 but also keep 18

I was running Ubuntu 16 LTS, foolishly decided to upgrade to 18 LTS (getting too close to EOL?).

18 broke the most important software I use, DVDSTYLER, as well as other less important things. Well, it removed the old DVDSTYLER and the new one crashes after starting The DVDSTYLER website told me that it is broken on 18, I have to upgrade to 19 for which there is no LTS so I’ll get stuck with yet another upgrade very soon, will never be fixed for 18. Ubuntu also didn’t seem to care.

I don’t want to upgrade again and break more stuff, and long term I have learned my lesson, always be prepared to go back, preferably not by a full partition restore. I plan to buy a new desktop and learn virtual machines so I can run multiple releases at the same time, as I was used to doing on mainframes….

So I copied my bootable partion from sdc8 to sdc9, update fstab (using /dev/sdc9 after being unable to update the UUID).

update-grub (runing on sdc8) lists that it found ubuntu 18.04 on sdc9, but when I boot it does not list the sdc9 option, only the sdc8 and an old version 13 that I had forgotten about on sdc1.

I can’t imagine I am the first person who wants to clone a partition then upgrade one of them, but could not find anyone else here.

I guess I could install a fresh copy of 19 on the sdc9, but I have 10+ years of stuff I’ve added to my 18 that I don’t remember everything there…

FYI, I also found a backlevel dvdstyler (just past the one I had been running on 16) but it needed many packages that I found eventually, but the then one I cannot find. It says it needs some program, not the package it is in, which makes it difficult and caused some shotgunning. I suppose I could try every release of DVDSTYLER to see if any of them will install or will use packages that I am able to find, and if I was sure that would work, I’d do it, but i lack confidence. Maybe I should ask on DVDSTYLER if there is a back level that works, but thought they would have just told me that if one did.

Can I pluck a polymorphed creature and keep its feathers? [duplicate]

This question already has an answer here:

  • What happens to a polymorphed character if he is shorn as a sheep? 1 answer

So this is a question about the polymorph and true polymorph spells. Both spells include in their description an explanation as to what happens to the gear of the target of the polymorph spells …

The target’s gear melds into the new form. The creature can’t activate, use, wield, or otherwise benefit from any of its equipment.

… but nothing about what happens if you take away a part of the creature, like a feather, does it disappear once the spell is over, do you keep it ?

This is probably a subjective matter who’s gonna gather subjective answers, but I don’t mind. I have found nothing in the SAC or the erratas about that and even tho my current GM has ruled that I could keep the feather of the hummingbird I had polymorphed into, but I also do feel like it’s a debate I could have with every future DM … might as well see what RPG Stack Exchange thinks ?

How to keep user logged in when using OpenID Connect & Cookies in dotnet core?

I’m working on an OpenID Connect Hybrid flow, basically the response type in my case is: code id_token Problem: I can’t seem to persist the session of the user when logged in using the id_token.

I built the app using .Net Core’s built in OpenID Connect authentication handler and Cookies handler. However, the cookies are session cookies, so they expire the moment the browser is closed, in which case the user is logged out and has to login again when he opens the browser. Which got me thinking, that I haven’t been using refresh tokens even though I’ve been asking for them from the Authorization server. So, the question to rule them all: How do I persist the user’s login on the browser so he will have to login just once? I realize Cookies should have an expiry date and not be regular session cookies and I also realize that I should be using refresh tokens to re-authenticate the user again behind the scenes and thus produce a new cookie in the process. However, Is my thinking right? If yes, how to do that ? If not, what did I get wrong?

Keep sticky posts in the main loop, at their regular place

I have a wordpress theme that has a place at the top for sticky posts. If a post is set to sticky, it will show up at the top, but it will not be in the posts listed below.

How can I have the sticky posts inside the main loop? I deleted this function which hid them from the main loop:

public function modify_main_query( $  query ) { if ( $  query->is_home() && $  query->is_main_query() ) { $  query->query_vars['post__not_in'] = $  this->sticky_posts; } } 

After deleting this, the posts show in the main loop, but they show up at the top of the 10 items, before the rest.

How can I have them show at their respective dates, as if they were NOT sticky?


Keep getting “SQLSTATE[HY000] [1045]” despite database credentials and permissions being correct

I’m trying to install Magento 2.3.1 locally, and I keep running into this error when I adding the database. The problem is not the credentials. Everything I’ve read about this error implies it’s a problem with the database name, user, or password. I’ve tried different databases and users – with and without passwords – and get the same result each time.

I was able to install Magento 2 once after uninstalling and reinstalling MAMP Pro. Then, I updated my PC, and the site was no longer working. Instead there was an error message telling me to view the details in the exceptions log. This is roughly how the first line of that log file said:

main.CRITICAL: exception 'PDOException' with message 'SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using password: YES) 

I deleted those site files and tried installing Magento again, and I was back to getting that error message. I don’t know what else to try. I’m not reinstalling MAMP Pro every time I restart my computer.

I have a somewhat unusual setup in that I use Windows 10 with MAMP Pro 4. I don’t know if that has something to do with it.