Blocking access for an individual user to a specific SP

[Mark Cairney]

Hi Scott,

It's more of a case of this being more than "add this config line/block"
and being something that requires careful planning and thought.

I realise that the v3 IdP and it's concept of flows is far more
configurable/customisable than previous versions of the software but
with this added flexibility comes complexity and abstraction.

95% of configuration changes to a production IdP will be simple
operations like modifying the attribute filter or adding metadata.

For the record we've ended up taking the non-technical approach and
engaged with the user directly.

On 26/09/2018 14:42, Cantor, Scott wrote:
>> Thanks for this. It looks a bit more complex to set up than I'd hoped and isn't
>> something we could just push into production.
> 
> I don't really know what to say to that, but that's as simple as the IdP gets now. You will find just about anything else much harder and more complex, so that doesn't bode well.
> 
> -- Scott
> 

-- 
/****************************

Mark Cairney
ITI Enterprise Services
Information Services
University of Edinburgh

Tel: 0131 650 6565
Email: Mark.Cairney at ed.ac.uk
PGP: 0x435A9621

*******************************/

The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.