Should accessURL be a mandatory attribute in the SP config?

[darshanasbg]

Right now accessURL is mandatory if only the Service Provider is discoverable.

accessURL is required to avoid other issues like,

• To avoid bookmark issue
• To avoid browser back button issue
• To avoid redirecting to dashboard\user-portal after self-registration with email validation. etc.

Thus, IMO accessURL should be a mandatory attribute in Service Provider.

Along with that, for better UX, it can make imageURL also mandatory. So all related UIs can use SP logo in consistent way without depending whether application is discoverable or not.

[thanujalk]

+1. Better make this mandatory.

[omindu]

@darshanasbg What's exactly meant by discoverable in this context?

Also, IMO keeping the imageURL should be kept optional and not a mandatory step in creating the SP.

[mefarazath]

It makes sense to make the accessURL mandatory.

But it doesn't sound right to mandate the imageURL.

So all related UIs can use SP logo in consistent way without depending whether application is discoverable or not.

Can't we have a generic image if the application doesn't specify an imageURL? That way all apps will have an image.

[darshanasbg]

It makes sense to make the accessURL mandatory.

But it doesn't sound right to mandate the imageURL.

So all related UIs can use SP logo in consistent way without depending whether application is discoverable or not.

Can't we have a generic image if the application doesn't specify an imageURL? That way all apps will have an image.

As of now, we can't have a default application image when we register the SP in management console.. We will have it in the Admin portal.

But we do we show a default application image (if 'imageURL' is not present), in the places we need to show an SP image (like, user-portal)..