Issue with residual access after deleting a service

Hello,
We are students working on implementing an identity-based access control project using OpenZiti.
We created a test website (HTTP-based) to test our setup. It worked correctly the first time, but later we wanted to delete and rebuild it.
When we deleted the service, we forgot to check the box for “delete all related work”.

After realizing this, we manually deleted everything we could find:
• Related identities
• Service policies (bind and dial)
• Configurations

However, the problem is still happening:
• The old website link is still accessible to everyone if they know the link.
• We cannot modify or fully remove it from the OpenZiti console anymore.

Can you please guide us on how to fix this?
We would appreciate any help. Thank you!

Hi @Deemaalbinali, welcome to the community and to OpenZiti!

Sounds like a fun project! make sure you share it here or on reddit/etc when you're done! :slight_smile:

There's no easy way to say this so forgive my directness in my response, but what you're describing really isn't possible. :slight_smile: What is possible is that your website is cached in a browser, or perhaps you are shadowing an actual URL that provides access.

If you're just starting out and you're in a real pickle, just deleting the controller and router and all associated files is the last resort way to clean everything up. Just make sure you get all the files (db, pki etc).

Instead of that, it's probably more instructive to diagnose the problem using command line tools.

Things to try:

  • Can you "curl" to the http-based service?
  • use ziti edge policy-advisor services|identities (services or identities or both if you want)

Can you use the ziti cli to list services, configs, service-policies, identities to see if something is left behind?